Re: ACPI device without physical node (pnpacpi oddity?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2015-12-01 at 18:03 -0800, Andy Lutomirski wrote:
> On Tue, Dec 1, 2015 at 6:00 PM, Zhang Rui <rui.zhang@xxxxxxxxx> wrote:
> > On Wed, 2015-12-02 at 01:48 +0100, Rafael J. Wysocki wrote:
> >> For your use case we could make the PNP layer ignore the pnp0c02 device id if
> >> (a) _CRS is missing and (b) pnp0c02 is in the _CID list (not a _HID).
> >>
> > Yes, this could work.
> > But I'm concerning another case, say, a device with both _CRS and _CID
> > "PNP0C02", we don't have a way to probe the device via _HID.
> 
> Doesn't .acpi_match_table do exactly this?
> 
I mean, even if _CRS is available, the device will be bound to the PNP
system driver (drivers/pnp/system.c) forever, thus you still cannot
write a new driver to probe INT33D5.

thanks,
rui


--
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



[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux