From: sashiko-bot@kernel.org
To: "Felix Radensky" <fradensky@nvidia.com>, linux-leds@vger.kernel.org
Cc: lee@kernel.org
Subject: Re: [PATCH] leds: mlxreg: Fix missing fan LEDs on systems reporting a unit count
Date: Wed, 21 Oct 2026 14:34:01 +0000 [thread overview]
Message-ID: <sashiko-outbox-180382@kernel.org> (raw)
In-Reply-To: <20261021142824.603605-1-fradensky@nvidia.com>
> From: Vadim Pasternak <vadimp@nvidia.com>
>
> LED platform data is shared between systems of the same family, and the
> driver registers only the LED instances that are actually present on the
> running system. The platform data entry names a capability register and
> a bit in it, and an entry whose bit is clear is skipped.
>
> The capability registers are a single byte wide, so a bitmap cannot
> describe more than eight units, which is not enough for systems with ten
> fan drawers. Recent CPLD revisions therefore report a count of the units
> present instead of a bitmap, and do so uniformly rather than only where
> the bitmap would overflow, leaving no per unit bit to test. Platform
> data describes such an entry by its 'slot', the one based index of the
> unit the LED belongs to, and leaves 'bit' at zero.
>
> [ ... ]
>
> Fixes: 783259e9b19d ("platform: mellanox: Introduce support of Nvidia smart switch")
>
> Signed-off-by: Vadim Pasternak <vadimp@nvidia.com>
> Signed-off-by: Felix Radensky <fradensky@nvidia.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261021142824.603605-1-fradensky@nvidia.com?part=1
prev parent reply other threads:[~2026-10-21 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 14:28 [PATCH] leds: mlxreg: Fix missing fan LEDs on systems reporting a unit count Felix Radensky
2026-10-21 14:34 ` sashiko-bot [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=sashiko-outbox-180382@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=fradensky@nvidia.com \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.