Changes between Version 88 and Version 89 of gsc

Timestamp:

09/15/2021 09:55:11 PM (3 years ago)

Author:

Tim Harvey

Comment:

removed setting of R11=0xff for user pushbutton examples and explain

gsc

@@ -151 +151 @@
 
 For more information see [#gsc-interrupts gsc-interrupts]
+
+Note that you should not be altering this register if you are using the Linux GSC driver as it will enable the interrupts according to other drivers that register handlers for them. Enabling interrupt sources that have no handlers will result in interrupt storms.
 
 [=#gsc_firmware_crc]
@@ -674 +676 @@
 #!bash
 i2cset -f -y 0 0x20 0 0x00 # disable pushbutton hard reset
-i2cset -f -y 0 0x20 11 0xff # enable all interrupts
 }}}
   * please see [#IRQ_GPIO_CHANGE here] regarding un-terminated inputs causing spurious GPIO_CHANGE events
@@ -1017 +1018 @@
 The Gateworks System Controller has an interrupt signal to the host processor which it asserts when an event has occurred worth notifying the host about. The [#gsc_interrupt_enable GSC_INTERRUPT_ENABLE_0 (R11)] register defines what events can trigger an interrupt and an interrupt service routine can query the [#gsc_interrupt_status GSC_INTERRUPT_STATUS_0 (R10)] register to see what events are present. The interrupt remains asserted until all status bits are cleared by writing 0's to those bits in the [#gsc_interrupt_status GSC_INTERRUPT_STATUS_0 (R10)] register.
 
+Note that you should not be altering the GSC_INTERRUPT_ENABLE_0 register if you are using the Linux GSC driver as it will enable the interrupts according to other drivers that register handlers for them. Enabling interrupt sources that have no handlers will result in interrupt storms.
+
 '''GSCv3''' has an additional pair of interrupt registers represented by [#GSC_INTERRUPT_STATUS_1 GSC_INTERRUPT_STATUS_1 (R17)] and [#GSC_INTERRUPT_ENABLE_1 GSC_INTERRUPT_ENABLE_1 (R18)].
 
@@ -1204 +1207 @@
 #!bash
 i2cset -f -y 0 0x20 0 0x00 # disable pushbutton hard reset
-i2cset -f -y 0 0x20 11 0xff # enable all interrupts
 }}}
   * please see [#IRQ_GPIO_CHANGE here] regarding un-terminated inputs causing spurious GPIO_CHANGE events