[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210528082852.62070024@dellmb>
Date: Fri, 28 May 2021 08:28:52 +0200
From: Marek Behún <marek.behun@....cz>
To: Andrew Lunn <andrew@...n.ch>
Cc: Marek Behún <kabel@...nel.org>,
linux-leds@...r.kernel.org, netdev@...r.kernel.org,
Pavel Machek <pavel@....cz>, Dan Murphy <dmurphy@...com>,
Russell King <linux@...linux.org.uk>,
Matthias Schiffer <matthias.schiffer@...tq-group.com>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Subject: Re: [PATCH leds v1 3/5] leds: trigger: netdev: move trigger data
structure to global include dir
On Thu, 27 May 2021 18:48:21 +0200
Andrew Lunn <andrew@...n.ch> wrote:
> On Wed, May 26, 2021 at 08:00:18PM +0200, Marek Behún wrote:
> > In preparation for HW offloading of netdev trigger, move struct
> > led_trigger_data into global include directory, into file
> > linux/ledtrig.h, so that drivers wanting to offload the trigger can
> > see the requested settings.
> >
> > Signed-off-by: Marek Behún <kabel@...nel.org>
> > ---
> > drivers/leds/trigger/ledtrig-netdev.c | 23 +---------------
> > include/linux/ledtrig.h | 38
> > +++++++++++++++++++++++++++
>
> I'm wondering how this is going to scale, if we have a lot of triggers
> which can be offloaded. Rather than try to pack them all into
> one header, would it make more sense to add
>
> include/linux/led/ledtrig-netdev.h
>
> Andrew
Hmm, I guess you are right. Also when looking at a LED controller
driver we could immediately see which triggers this driver can offload,
when looking at headers included.
Powered by blists - more mailing lists