From: Pavel Machek <pavel@ucw.cz>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: "linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: pending patches
Date: Sun, 12 Sep 2021 09:11:07 +0200 [thread overview]
Message-ID: <20210912071107.GA16081@amd> (raw)
In-Reply-To: <BN9PR12MB53811FD7FC0C8DD410F785CEAFD89@BN9PR12MB5381.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
Hi!
> > > I have two pending patches:
> > > https://patches.linaro.org/patch/432324/ from 2021-05-07
> >
> > I don't understand this one. Are these normal single-color LEDs, or is it some
> > kind of weird red/orange/amber/green combination exposed as single LED?
>
> This is not single-color LED. LED is controlled by programmable device, color is
> set by writing relevant bit mask combination to the related LED register.
Not a single-color LED yet using single-color API, and now you are
introducing additional hacks on the top of it. Sorry, no.
> > > https://patches.linaro.org/patch/403538/ from 2021-03-16, which has been
> > re-sent.
> >
> > In this case, I don't think i2c bus number is suitable way to identify add-on
> > card. Having some way of identifying add-on cards makes sense (as we'll
> > probably have other vendors having "fault" or "activity"
> > light on their cards), but those boards will not neccessarily have i2c on them.
>
> Line card always has I2C connection, LED color is controlled through a programmable
> device, which is always I2C device. So, this is I2C and bus number identifies topology.
I see it works for your hardware. I don't believe it works for other
vendors having "activity" LED on their card, and I'd like to see
consistent naming across vendors.
> Pavel,
> I have those patches pending very long time. Could you, please, help to get them
> accepted?
Not really, sorry.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2021-09-12 7:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 18:56 pending patches Vadim Pasternak
2021-08-20 8:06 ` Pavel Machek
2021-09-12 5:06 ` Vadim Pasternak
2021-09-12 7:11 ` Pavel Machek [this message]
2021-09-12 8:08 ` Vadim Pasternak
-- strict thread matches above, loose matches on Subject: below --
2016-07-13 17:06 Pending patches Denys Dmytriyenko
2014-08-25 18:40 Denys Dmytriyenko
2012-02-21 12:10 Robert Jarzmik
2012-02-22 7:28 ` Sascha Hauer
2010-04-01 15:21 Alan Stern
2009-07-15 18:01 Alan Stern
2009-07-16 1:02 ` James Bottomley
2009-07-16 14:07 ` Alan Stern
2009-07-31 19:05 ` Alan Stern
2009-01-13 16:43 Alan Stern
2008-04-12 16:41 Felipe Balbi
2008-04-14 18:05 ` Tony Lindgren
2008-02-04 9:33 Mauro Carvalho Chehab
2007-08-07 19:26 pending patches Yoshinori K. Okuji
2007-08-12 14:52 ` Robert Millan
2007-08-21 12:16 ` tgingold
2007-08-22 12:05 ` Johan Rydberg
2005-12-27 9:51 Pending patches Dirk Behme
2005-12-27 18:01 ` Anderson.Briglia
2005-12-28 15:53 ` Anderson Lizardo
2005-12-30 22:28 ` Tony Lindgren
2005-09-06 20:17 Alan Stern
2005-09-06 20:28 ` Patrick Mansfield
2005-09-06 20:43 ` Alan Stern
2005-09-07 14:47 ` James Bottomley
2005-09-07 19:42 ` Mike Anderson
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=20210912071107.GA16081@amd \
--to=pavel@ucw.cz \
--cc=linux-leds@vger.kernel.org \
--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.