Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1212694

Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name

From Dustin Byford <dustin@cumulusnetworks.com>
Newsgroups linux.kernel
Subject Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name
Date 2015-08-25 07:10 +0200
Message-ID <q1eEF-55e-9@gated-at.bofh.it> (permalink)
References <pXsZA-3ac-21@gated-at.bofh.it> <pXLpw-5eo-11@gated-at.bofh.it> <pYnEu-1sk-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon Aug 17 11:00, Jarkko Nikula wrote:

> If I remember correctly ACPI ID should not ever change and instance id :xy
> after INTABCD:xy should also be visible and keep the order even if device is
> disabled or not plugged. But I'm not absolute sure about this.
> 
> At least on a test platform that allow disable devices will show those
> devices off-line (/sys/bus/acpi/devices/INTABCD:xy/status == 0).

I'm always surprised how hard it is to tell what *can't* happen in ACPI.
How about a conditional call to LoadTable()?  Seems like that would mess
up the :xy.  Moot point, I think you're on the right track in your RFC
patch.

		--Dustin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next | Find similar | Unroll thread


Thread

Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name Dustin Byford <dustin@cumulusnetworks.com> - 2015-08-25 07:10 +0200

csiph-web