From: "Dall, Betty" <betty.dall@hpe.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI/device_sysfs: Add sysfs support for _HRV hardware revision
Date: Wed, 27 Apr 2016 16:15:30 +0000 [thread overview]
Message-ID: <AT5PR84MB0083E24D7512C359906A09489D640@AT5PR84MB0083.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <3691881.pb3S7Il1cr@vostro.rjw.lan>
On 04/26/2016 02:33 PM, Rafael J. Wysocki wrote:
> On Wednesday, April 13, 2016 08:48:14 AM Betty Dall wrote:
>> The ACPI _HRV object on the device is used to supply Linux with
>> the device's hardware revision. This is an optional object. Add
>> sysfs support for the _HRV object if it exists on the device.
>>
>> Signed-off-by: Betty Dall <betty.dall@hpe.com>
>
> The patch itself looks OK to me, but why exactly do we need that thing in sysfs?
>
> Thanks,
> Rafael
>
Hi Rafael,
I am working on a platform where non-PCI hardware is changing quickly
and users want to check what hardware version they are running on. For
example, someone checks out a lab system and wants to see if the device
is the latest version or if it needs to be updated - they could cat the
sysfs hrv file to find the version. It is most useful for non-PCI
devices because lspci can list the hardware version for PCI devices; PCI
devices in my testing don't supply _HRV. But, there is not an easy
solution for non-PCI devices to get the hardware revision from user
space with out this hrv sysfs patch.
Originally, I added the sysfs hrv to my specific device driver. On
review, I thought it would a good improvement for all devices that have
an _HRV.
Thanks,
Betty
next prev parent reply other threads:[~2016-04-27 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 14:48 Betty Dall
2016-04-26 20:35 ` Rafael J. Wysocki
2016-04-27 16:15 ` Dall, Betty [this message]
2016-04-27 21:19 ` Rafael J. Wysocki
2016-04-26 20:41 ` Rafael J. Wysocki
2016-04-27 16:19 ` Dall, Betty
2016-04-27 21:21 ` Rafael J. Wysocki
2016-04-29 13:55 ` Dall, Betty
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=AT5PR84MB0083E24D7512C359906A09489D640@AT5PR84MB0083.NAMPRD84.PROD.OUTLOOK.COM \
--to=betty.dall@hpe.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®