On Tuesday, September 16th, 2025 at 18:07, Lee Jones <[email protected]> wrote:
>
>
> On Tue, 16 Sep 2025, Bjorn Andersson wrote:
>
> > On Thu, Sep 11, 2025 at 11:01:00AM +0200, Hans de Goede wrote:
> >
> > > Hi Lee,
> > >
> > > On 11-Sep-25 10:15 AM, Lee Jones wrote:
> > >
> > > > On Wed, 10 Sep 2025, Aleksandrs Vinarskis wrote:
> > > >
> > > > > From: Hans de Goede [email protected]
> > > > >
> > > > > Add 'name' argument to of_led_get() such that it can lookup LEDs in
> > > > > devicetree by either name or index.
> > > > >
> > > > > And use this modified function to add devicetree support to the
> > > > > generic
> > > > > (non devicetree specific) [devm_]led_get() function.
> > > > >
> > > > > This uses the standard devicetree pattern of adding a -names string
> > > > > array
> > > > > to map names to the indexes for an array of resources.
> > > > >
> > > > > Reviewed-by: Andy Shevchenko [email protected]
> > > > > Reviewed-by: Lee Jones [email protected]
> > > >
> > > > Remind me why this can't go in through LED again?
> > >
> > > I don't think anyone has discussed how to merge this yet.
> > >
> > > I believe that the LED tree is the correct tree to merge this
> > > entire series through, once the DT bits have been reviewed.
> >
> > Unless there are some strong reasons (that I'm failing to spot), we
> > should merge the DeviceTree binding and implementation through the LED
> > tree. Then I merge the DTS change through the Qualcomm DT tree once the
> > bindings are available in linux-next.
Hi Bjorn,
The bindings are now in linux-next. Could you please pick the DTS change?
Thanks,
Alex
>
>
> 1-3 have been applied to the LED tree already.
>
> --
> Lee Jones [李琼斯]
