From: Pavel Machek <pavel@ucw.cz>
To: Tony Hutter <hutter2@llnl.gov>, linux-leds@vger.kernel.org
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Lukas Wunner <lukas@wunner.de>,
mariusz.tkaczyk@linux.intel.com, minyard@acm.org,
linux-pci@vger.kernel.org,
openipmi-developer@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 RESEND] PCI: Introduce Cray ClusterStor E1000 NVMe slot LED driver
Date: Mon, 19 May 2025 12:51:30 +0200 [thread overview]
Message-ID: <aCsNMvfSWptltx5k@duo.ucw.cz> (raw)
In-Reply-To: <553813b6-1d44-488c-b41b-4be08e1c1733@llnl.gov>
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
Hi!
> Add driver to control the NVMe slot LEDs on the Cray ClusterStor E1000.
> The driver provides hotplug attention status callbacks for the 24 NVMe
> slots on the E1000. This allows users to access the E1000's locate and
> fault LEDs via the normal /sys/bus/pci/slots/<slot>/attention sysfs
> entries. This driver uses IPMI to communicate with the E1000 controller
> to toggle the LEDs.
>
> Signed-off-by: Tony Hutter <hutter2@llnl.gov>
We have LED subsystem.
> +++ b/Documentation/ABI/testing/sysfs-bus-pci
> @@ -231,6 +231,27 @@ Description:
> - scXX contains the device subclass;
> - iXX contains the device class programming interface.
>
> +What: /sys/bus/pci/slots/.../attention
> +Date: February 2025
> +Contact: linux-pci@vger.kernel.org
> +Description:
> + The attention attribute is used to read or write the attention
> + status for an enclosure slot. This is often used to set the
> + slot LED value on a NVMe storage enclosure.
> +
> + Common values:
> + 0 = OFF
> + 1 = ON
> + 2 = blink (ampere, ibmphp, pciehp, rpaphp, shpchp)
> +
> + Using the pciehp_craye1k extensions:
> + 0 = fault LED OFF, locate LED OFF
> + 1 = fault LED ON, locate LED OFF
> + 2 = fault LED OFF, locate LED ON
> + 3 = fault LED ON, locate LED ON
> +
> + Other values are no-op, OFF, or ON depending on the driver.
> +
And this should use it.
Best regards,
Pavel
--
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, and Musk!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-05-19 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 0:21 [PATCH v3 RESEND] PCI: Introduce Cray ClusterStor E1000 NVMe slot LED driver Tony Hutter
2025-05-19 10:51 ` Pavel Machek [this message]
2025-05-20 21:26 ` Tony Hutter
2025-05-21 8:22 ` ALOK TIWARI
-- strict thread matches above, loose matches on Subject: below --
2025-02-26 1:13 [PATCH v3] " Tony Hutter
2025-04-04 22:16 ` [PATCH v3 RESEND] " Tony Hutter
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=aCsNMvfSWptltx5k@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=helgaas@kernel.org \
--cc=hutter2@llnl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.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 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.