[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150825050329.GC21569@cumulusnetworks.com>
Date: Mon, 24 Aug 2015 22:03:29 -0700
From: Dustin Byford <dustin@...ulusnetworks.com>
To: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
Cc: Guenter Roeck <linux@...ck-us.net>,
Wolfram Sang <wsa@...-dreams.de>, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, jdelvare@...e.com,
lm-sensors@...sensors.org, rjw@...ysocki.net,
linux-acpi@...r.kernel.org
Subject: Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists