public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Cc: Tony Hutter <hutter2@llnl.gov>,
	bhelgaas@google.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] PCI: Introduce Cray ClusterStor E1000 NVMe slot LED driver
Date: Thu, 5 Sep 2024 10:56:29 -0500	[thread overview]
Message-ID: <20240905155629.GA389032@bhelgaas> (raw)
In-Reply-To: <20240905081925.00001d14@linux.intel.com>

On Thu, Sep 05, 2024 at 08:19:25AM +0200, Mariusz Tkaczyk wrote:
> On Tue, 3 Sep 2024 17:18:20 -0500
> Bjorn Helgaas <helgaas@kernel.org> wrote:
> 
> > On Tue, Aug 27, 2024 at 02:03:48PM -0700, Tony Hutter wrote:
> > > 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.  
> > 
> > I hope/assume the interface is the same as one of the others, i.e.,
> > the existing one added for NVMe behind VMD by
> > https://git.kernel.org/linus/576243b3f9ea ("PCI: pciehp: Allow
> > exclusive userspace control of indicators") or the new one for NPEM
> > and the _DSM at
> > https://lore.kernel.org/linux-pci/20240814122900.13525-3-mariusz.tkaczyk@linux.intel.com/
> > 
> > I suppose we intend that the ledmon utility will be able to drive
> > these LEDs?  Whatever the user, we should try to minimize the number
> > of different interfaces for this functionality.
> 
> Ledmon won't support it, at least not in current form. Ledmon
> support for pciehp attention is limited to VMD, i.e. first we must
> find VMD driver then we are looking for slot/attention.  I'm not
> familiar with any attempt to add support for this in ledmon.
> 
> From the end user perspective, I don't like pciehp/attention because
> we are refereeing to pciehp driver not pcieport and to determine
> proper slot we need to do additional matching by slot/address. I
> would be simpler.
> https://github.com/intel/ledmon/blob/main/src/lib/vmdssd.c#L100

All I'm trying to say is that NPEM, the related _DSM, and the VMD
special case are all ways to control NVMe slot IDs.  This Cray thing
is another.  We already have two user interfaces (the NPEM/_DSM one
and the VMD one), and I'd like to avoid adding a third.

      reply	other threads:[~2024-09-05 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27 21:03 [PATCH] PCI: Introduce Cray ClusterStor E1000 NVMe slot LED driver Tony Hutter
2024-09-01  8:25 ` Lukas Wunner
2024-09-03 22:18 ` Bjorn Helgaas
2024-09-05  6:19   ` Mariusz Tkaczyk
2024-09-05 15:56     ` Bjorn Helgaas [this message]

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=20240905155629.GA389032@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=hutter2@llnl.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox