From: stuart hayes <stuart.w.hayes@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org
Subject: Re: [PATCH] Add support for PCIe SSD status LED management
Date: Wed, 5 May 2021 11:01:56 -0500 [thread overview]
Message-ID: <9fa180bd-67d2-dbf7-4fa4-e9838b2ec830@gmail.com> (raw)
In-Reply-To: <20210416192010.3197-1-stuart.w.hayes@gmail.com>
On 4/16/2021 2:20 PM, Stuart Hayes wrote:
> This patch adds support for the PCIe SSD Status LED Management
> interface, as described in the "_DSM Additions for PCIe SSD Status LED
> Management" ECN to the PCI Firmware Specification revision 3.2.
>
> It will add a single (led_classdev) LED for any PCIe device that has the
> relevant _DSM. The ten possible status states are exposed using
> attributes current_states and supported_states. Reading current_states
> (and supported_states) will show the definition and value of each bit:
>
>> cat /sys/class/leds/0000:88:00.0::pcie_ssd_status/supported_states
> ok 0x0004 [ ]
> locate 0x0008 [*]
> fail 0x0010 [ ]
> rebuild 0x0020 [ ]
> pfa 0x0040 [ ]
> hotspare 0x0080 [ ]
> criticalarray 0x0100 [ ]
> failedarray 0x0200 [ ]
> invaliddevice 0x0400 [ ]
> disabled 0x0800 [ ]
> --
> supported_states = 0x0008
>
>> cat /sys/class/leds/0000:88:00.0::pcie_ssd_status/current_states
> locate 0x0008 [ ]
> --
> current_states = 0x0000
>
> Signed-off-by: Stuart Hayes <stuart.w.hayes@gmail.com>
Any comments? I think I sent at a bad time originally. Thanks!
next prev parent reply other threads:[~2021-05-05 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 19:20 [PATCH] Add support for PCIe SSD status LED management Stuart Hayes
2021-05-05 16:01 ` stuart hayes [this message]
2021-05-05 16:12 ` Keith Busch
[not found] ` <CAL5oW00Pmnhqi1KZ9-jqFwLXQWBO0ddCyv+dr6qkry7iqZNQsw@mail.gmail.com>
2021-05-24 18:56 ` stuart hayes
2021-05-06 1:48 ` Krzysztof Wilczyński
2021-05-06 2:34 ` Keith Busch
2021-05-06 2:46 ` Krzysztof Wilczyński
2021-05-06 21:04 ` stuart hayes
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=9fa180bd-67d2-dbf7-4fa4-e9838b2ec830@gmail.com \
--to=stuart.w.hayes@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).