From: Pavel Machek <pavel@ucw.cz>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: Marek Behun <marek.behun@nic.cz>,
"jacek.anaszewski@gmail.com" <jacek.anaszewski@gmail.com>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH led-next 1/1] leds: mlxreg: Allow multi-instantiation of same name LED for modular systems
Date: Thu, 8 Oct 2020 09:56:19 +0200 [thread overview]
Message-ID: <20201008075619.GB32424@amd> (raw)
In-Reply-To: <DM6PR12MB38986A442F12A2DFB5769235AF0B0@DM6PR12MB3898.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]
Hi!
> > > > It could be more than one instance of LED with the same name in the
> > > > modular systems. For example, "status" or "uid" LED can be located
> > > > on chassis and on each line card of modular system.
> > > > In order to avoid conflicts with duplicated names, append platform
> > > > device Id, which is unquie, to LED name after driver name.
> > > > Thus, for example, "status" LED on chassis is to be called, like it
> > > > is called now on non modular systems, on which platform device Id is
> > > > not
> > > > specified: "mlxreg:status:green". While for the line cards LEDs it
> > > > will be called like: "mlxreg48:status:green",
> > > > "mlxreg66:status:green", etcetera.
> > >
> > > No.
> > >
> > > You really should not have mlxreg: in the LED label. It is useless.
>
> 'mlxreg' is device name, which could be CPLD or FPGA.
> It should be in label.
No.
You can try to explain what "mlxreg" means, but...
You can get away with "eth0" as a device name. We should talk about
"switch0" I guess.
> There also few other reasons for that.
>
> This name is used in thousands system in the field and
> customers use it in their application.
That may be reason not to change existing names.
> We used to provide our ASIC and CPLD or FPGA logic
> (Verilog) to ODM vendors, which build their own switch
> on top of it and use our drivers. So, the can implement
> additional LED on their switches, not controlled by our
> drivers and device name 'mlxreg' allows to distinct between
> LED objects.
>
> Actually name like 'mlxreg48', 'mlxreg56' are yet another
> 'mlxreg' devices with appended physical bus Id.
But noone is currently using mlxreg123 in their applications, so that
part is not going in.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-10-08 7:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 16:58 [PATCH led-next 1/1] leds: mlxreg: Allow multi-instantiation of same name LED for modular systems Vadim Pasternak
2020-10-06 23:15 ` Marek Behun
2020-10-07 6:07 ` Vadim Pasternak
2020-10-07 12:17 ` Marek Behun
2020-10-07 11:31 ` Pavel Machek
2020-10-07 12:20 ` Marek Behun
2020-10-08 6:16 ` Vadim Pasternak
2020-10-08 7:56 ` Pavel Machek [this message]
2020-10-08 8:47 ` Vadim Pasternak
2020-10-08 8:55 ` Marek Behun
2020-10-08 9:30 ` Vadim Pasternak
2020-10-08 10:05 ` Pavel Machek
2020-10-08 10:32 ` Vadim Pasternak
2020-11-25 11:20 ` Pavel Machek
2020-11-25 12:01 ` Vadim Pasternak
2020-12-30 18:48 ` Pavel Machek
2020-10-08 10:32 ` Marek Behun
2020-10-12 10:14 ` Vadim Pasternak
2020-10-21 8:33 ` Pavel Machek
2020-10-21 12:29 ` Vadim Pasternak
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=20201008075619.GB32424@amd \
--to=pavel@ucw.cz \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=vadimp@nvidia.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.