Zhao Yakui wrote:
a. EC GPE storm. According to ACPI spec the EC uses the pulse interrupt and interrupt is firmware generated using an EC GPIO output, which is connected with chipset GPIO input. If the pulse waveform is very wide, maybe several EC GPE interrupts will be triggered although EC firmware generates one pulse waveform. How can we read the corresponding data from EC in the GPE interrupt service handler? Maybe the read/write data is completely incorrect.
Sorry, I missed the whole idea on first reading :) You've started talking hardware terms :) EC in our case exposes two I/O ports 0x62 (status/command) and 0x66 (data r/w). It always exposes two, but numbers sometime differ... We always did status read in interrupt context, which is inb(0x62), and always relayed on that being working. Now you are telling that there is a huge difference between that and inb(0x66), which will accomplish EC_READ command. So, could you please tell, how reading of port 0x62 might be all good from interrupt context, and reading of port 0x66 is completely wrong idea? Regards, Alex. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
