From: Dustin Byford <dustin-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
To: Jarkko Nikula <jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jdelvare-IBi9RG/b67k@public.gmane.org,
lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org,
rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC 0/1] i2c: acpi: revert setting a "stable" device name
Date: Mon, 24 Aug 2015 22:03:29 -0700 [thread overview]
Message-ID: <20150825050329.GC21569@cumulusnetworks.com> (raw)
In-Reply-To: <55D1948C.6080501-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
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
WARNING: multiple messages have this Message-ID (diff)
From: Dustin Byford <dustin@cumulusnetworks.com>
To: Jarkko Nikula <jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jdelvare-IBi9RG/b67k@public.gmane.org,
lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org,
rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [lm-sensors] [RFC 0/1] i2c: acpi: revert setting a "stable" device name
Date: Tue, 25 Aug 2015 05:03:29 +0000 [thread overview]
Message-ID: <20150825050329.GC21569@cumulusnetworks.com> (raw)
In-Reply-To: <55D1948C.6080501-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
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
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
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
Date: Mon, 24 Aug 2015 22:03:29 -0700 [thread overview]
Message-ID: <20150825050329.GC21569@cumulusnetworks.com> (raw)
In-Reply-To: <55D1948C.6080501@linux.intel.com>
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
next prev parent reply other threads:[~2015-08-25 5:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 19:37 [RFC 0/1] i2c: acpi: revert setting a "stable" device name Dustin Byford
2015-08-14 19:37 ` Dustin Byford
2015-08-14 19:37 ` [lm-sensors] " Dustin Byford
2015-08-14 19:37 ` [RFC 1/1] " Dustin Byford
2015-08-14 19:37 ` [lm-sensors] " Dustin Byford
2015-08-15 15:13 ` [RFC 0/1] " Guenter Roeck
2015-08-15 15:13 ` [lm-sensors] " Guenter Roeck
2015-08-17 8:00 ` Jarkko Nikula
2015-08-17 8:00 ` [lm-sensors] " Jarkko Nikula
[not found] ` <55D1948C.6080501-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-08-25 5:03 ` Dustin Byford [this message]
2015-08-25 5:03 ` Dustin Byford
2015-08-25 5:03 ` [lm-sensors] " Dustin Byford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150825050329.GC21569@cumulusnetworks.com \
--to=dustin-quqiamftcip+xzjcv9emoeeocmrvltnr@public.gmane.org \
--cc=jarkko.nikula-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=jdelvare-IBi9RG/b67k@public.gmane.org \
--cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lm-sensors-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.