From: Tobias Waldekranz <tobias@waldekranz•com>
To: Andrew Lunn <andrew@lunn•ch>
Cc: davem@davemloft•net, kuba@kernel•org, f.fainelli@gmail•com,
olteanv@gmail•com, netdev@vger•kernel.org
Subject: Re: [PATCH net-next 1/2] net: dsa: mv88e6xxx: Add LED infrastructure
Date: Wed, 03 Jan 2024 15:27:24 +0100 [thread overview]
Message-ID: <87jzoq7ar7.fsf@waldekranz.com> (raw)
In-Reply-To: <8f9b8a8f-6741-4676-900a-e5832eb31fba@lunn.ch>
On ons, jan 03, 2024 at 15:09, Andrew Lunn <andrew@lunn•ch> wrote:
> On Wed, Jan 03, 2024 at 11:33:50AM +0100, Tobias Waldekranz wrote:
>> Parse LEDs from DT and register them with the kernel, for chips that
>> support it. No actual implementations exist yet, they will be added in
>> upcoming commits.
>
> Hi Tobias
>
> There are three of us now working on this. Linus, you and me. We all
> have different implementations.
Oh, sorry about that. I should have done the proper research before
posting :)
> What i don't like about this is that is has code which is going to be
> repeated in all DSA drivers, and even in all MAC drivers. I've already
> posted one patch series which added generic DSA support for LEDs, and
> some basic mv88e6xxx code. It got NACKed by Vladimir. So i'm slowly
> working on making it more generic, so it can be used by any MAC
> driver.
>
> I will try to post it in the next couple of days.
Interesting! I'll keep an eye out for it.
next prev parent reply other threads:[~2024-01-03 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 10:33 [PATCH net-next 0/2] net: dsa: mv88e6xxx: Add LED support for 6393X Tobias Waldekranz
2024-01-03 10:33 ` [PATCH net-next 1/2] net: dsa: mv88e6xxx: Add LED infrastructure Tobias Waldekranz
2024-01-03 14:09 ` Andrew Lunn
2024-01-03 14:27 ` Tobias Waldekranz [this message]
2024-01-03 23:03 ` kernel test robot
2024-01-04 0:15 ` kernel test robot
2024-01-03 10:33 ` [PATCH net-next 2/2] net: dsa: mv88e6xxx: Add LED support for 6393X Tobias Waldekranz
2024-01-04 3:16 ` kernel test robot
2024-01-04 22:01 ` kernel test robot
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=87jzoq7ar7.fsf@waldekranz.com \
--to=tobias@waldekranz$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=olteanv@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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