MCURTC:PublishNotifications: Difference between revisions

Line 9:

|-

| 1

| ~~Notification~~ bitmask

| [[I2C_Registers#Device_3|Interrupt bitmask]]

|}

Line 26:

=Description=

This ~~publishes~~ MCU ~~notifications based on~~ the ~~bitmask provided~~. Depending on the ~~notification ID~~, mcu~~-module~~ can publish "srv" notifications (using [[SRV:PublishToSubscriber|PublishToSubscriber]]) ~~or use its own internal event system for mcu::GPU, mcu::HID and mcu::RTC clients~~.

This triggers a software MCU interrupt in the mcu sysmodule. Depending on the bitmask, the mcu sysmodule can publish srv notifications (using [[SRV:PublishToSubscriber|PublishToSubscriber]]).

If value 0xFFFFFFFF (-1) is passed, mcu~~-module~~ will instead ~~ask~~ the ~~i2c~~ MCU ~~device for notifications~~.

If value 0xFFFFFFFF (-1) is passed, mcu sysmodule will instead read the [[I2C_Registers#Device_3|MCU interrupt field]].

@@ Line 9: / Line 9: @@
 |-
 | 1
-| Notification bitmask
+| [[I2C_Registers#Device_3|Interrupt bitmask]]
 |}
@@ Line 26: / Line 26: @@
 =Description=
-This publishes MCU notifications based on the bitmask provided. Depending on the notification ID, mcu-module can publish "srv" notifications (using [[SRV:PublishToSubscriber|PublishToSubscriber]]) or use its own internal event system for mcu::GPU, mcu::HID and mcu::RTC clients.
+This triggers a software MCU interrupt in the mcu sysmodule. Depending on the bitmask, the mcu sysmodule can publish srv notifications (using [[SRV:PublishToSubscriber|PublishToSubscriber]]).
-If value 0xFFFFFFFF (-1) is passed, mcu-module will instead ask the i2c MCU device for notifications.
+If value 0xFFFFFFFF (-1) is passed, mcu sysmodule will instead read the [[I2C_Registers#Device_3|MCU interrupt field]].