Date: Mon, 24 Aug 2015 22:03:29 -0700
From: Dustin Byford <dustin@cumulusnetworks.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: Guenter Roeck <linux@roeck-us.net>, Wolfram Sang <wsa@the-dreams.de>,
        linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
        jdelvare@suse.com, lm-sensors@lm-sensors.org, rjw@rjwysocki.net,
        linux-acpi@vger.kernel.org
Subject: Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name
Message-ID: <20150825050329.GC21569@cumulusnetworks.com>
References: <1439581034-5972-1-git-send-email-dustin@cumulusnetworks.com>
 <20150815151302.GA10020@roeck-us.net>
 <55D1948C.6080501@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <55D1948C.6080501@linux.intel.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 889
Lines: 20

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/