On Wed, 2015-09-23 at 16:56 -0700, Hanjun Guo wrote: > > It really depends on the people who writing the ASL code (DSDT), > I'm not sure if Windows will use _DSD and how to use it, but > firmware guys may just use the device ID to make the firmware > to be usable both by Linux and Windows, and that's reasonable > I think.
And the ideal way to do that is to add a _CID of "PRP0001" and a compatible string, and then Linux doesn't need to care about the special new HID that you've added purely to pander to the limitations of Windows. That way, once drivers are converted from the legacy of-property APIs to the new device-property APIs, there should be *nothing* required to make device drivers work under ACPI. That was kind of the point. If people want to add HIDs, fine. But let's not go down a path which *requires* modifying drivers. (I'm planning to try to learn Coccinelle and do a bombing run convertin to the new API some time soon, FWIW). -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
