From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@linux.intel.com>
To: Dan Williams <dan.j.williams@intel.com>,
stuart hayes <stuart.w.hayes@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"helgaas@kernel.org" <helgaas@kernel.org>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"kw@linux.com" <kw@linux.com>,
"lukas@wunner.de" <lukas@wunner.de>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"pavel@ucw.cz" <pavel@ucw.cz>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v3] Add support for PCIe SSD status LED management
Date: Thu, 7 Oct 2021 13:32:39 +0200 [thread overview]
Message-ID: <19dcfbea-efcd-b385-4031-23fae5c1c78b@linux.intel.com> (raw)
In-Reply-To: <CAPcyv4iig5rxCNb7GyGV9akhZKLF+OeGhewSbOeAzzA6pKreRA@mail.gmail.com>
On 06.10.2021 22:15, Dan Williams wrote:
>>>> +static struct led_state led_states[] = {
>>>> + { .name = "ok", .bit = 2 },
>>>> + { .name = "locate", .bit = 3 },
>>>> + { .name = "failed", .bit = 4 },
>>>> + { .name = "rebuild", .bit = 5 },
>>>> + { .name = "pfa", .bit = 6 },
>>>> + { .name = "hotspare", .bit = 7 },
>>>> + { .name = "ica", .bit = 8 },
>>>> + { .name = "ifa", .bit = 9 },
>>>> + { .name = "invalid", .bit = 10 },
>>>> + { .name = "disabled", .bit = 11 },
>>>> +};
>>> include/linux/enclosure.h has common ABI definitions of industry
>>> standard enclosure LED settings. The above looks to be open coding the
>>> same?
>>>
>> The LED states in inluce/linux/enclosure.h aren't exactly the same...
>> there are states defined in NPEM/_DSM that aren't defined in
>> enclosure.h. In addition, while the enclosure driver allows "locate" to
>> be controlled independently, it looks like it will only allow a single
>> state (unsupported/ok/critical/etc) to be active at a time, while the
>> NPEM/_DSM allow all of the state bits to be independently set or
>> cleared. Maybe only one of those states would need to be set at a time,
>> I don't know, but that would impose a limitation on what NPEM/_DSM can
>> do. I'll take a closer look at this as an alternative to using
>> drivers/leds/led-class.c.
> Have a look. Maybe Mariusz can weigh in here with his experience with
> ledmon with what capabilities ledmon would need from this driver so we
> can decide what if any extensions need to be made to the enclosure
> infrastructure?
Hmm... In ledmon we are expecting one state to be set at the time. So,
I would expected from kernel to work the same.
Looking into ledmon code, all capabilities from this list could be
used[1].
>>>> + { .name = "ok", .bit = 2 },
>>>> + { .name = "locate", .bit = 3 },
>>>> + { .name = "failed", .bit = 4 },
>>>> + { .name = "rebuild", .bit = 5 },
>>>> + { .name = "pfa", .bit = 6 },
>>>> + { .name = "hotspare", .bit = 7 },
>>>> + { .name = "ica", .bit = 8 },
>>>> + { .name = "ifa", .bit = 9 },
[1]https://github.com/intel/ledmon/blob/master/src/ibpi.h#L60
Thanks,
Mariusz
next prev parent reply other threads:[~2021-10-07 11:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 21:36 [PATCH v3] Add support for PCIe SSD status LED management Stuart Hayes
2021-08-14 6:23 ` Lukas Wunner
2021-10-04 17:41 ` stuart hayes
2021-10-05 4:41 ` Williams, Dan J
2021-08-18 7:05 ` Pavel Machek
2021-10-04 18:04 ` stuart hayes
2021-10-05 5:14 ` Williams, Dan J
2021-10-06 2:42 ` stuart hayes
2021-10-06 20:15 ` Dan Williams
2021-10-07 8:24 ` Pavel Machek
2021-10-07 11:32 ` Tkaczyk, Mariusz [this message]
2021-11-02 16:23 ` stuart hayes
2021-11-06 2:52 ` Dan Williams
2021-11-07 14:40 ` James Bottomley
2021-11-12 0:56 ` Krzysztof Wilczyński
2021-11-25 22:13 ` Bjorn Helgaas
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=19dcfbea-efcd-b385-4031-23fae5c1c78b@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=helgaas@kernel.org \
--cc=kbusch@kernel.org \
--cc=kw@linux.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=pavel@ucw.cz \
--cc=stuart.w.hayes@gmail.com \
/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.