Hi Nick, Duncan, On Wed, Jan 23, 2019 at 11:33:22AM -0700, Nick Crews wrote: > From: Duncan Laurie <dlaurie@xxxxxxxxxx> > > The Wilco Embedded Controller can return extended events that > are not handled by standard ACPI objects. These events can > include hotkeys which map to standard functions like brightness > controls, or information about EC controlled features like the > charger or battery. > > These events are triggered with an ACPI Notify(0x90) and the > event data buffer is read through an ACPI method provided by > the BIOS which reads the event buffer from EC RAM. > > These events are then processed, with hotkey events being sent > to the input subsystem and other events put into a queue which > can be read by a userspace daemon via a sysfs attribute. I thought we agreed that brightness keys will be routed through normal keyboard interface, not separate input device? Looking at the driver more, I do not see why it needs to be toed to EC, this seems to be a straightforward ACPI driver that should bind to and ACPI device by its HID, since the only thing it does is installing ACPI notify handler and shuffling the events over to userspace. I do not think we want to use a binary attribute for this, as it does not support polling well and in general is not well suitable for pumping data to userspace. I'd recommend char misc device for that. What kind of events will be delivered over this interface? Thanks. -- Dmitry
