[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 3 Mar 2024 10:48:36 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Andy Shevchenko <andy@...nel.org>
Cc: Chris Packham <chris.packham@...iedtelesis.co.nz>, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org, andrew@...n.ch,
gregory.clement@...tlin.com, sebastian.hesselbarth@...il.com, pavel@....cz,
lee@...nel.org, linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 4/4] ARM: dts: marvell: Indicate USB activity on x530
Hi Andy,
On Fri, Mar 1, 2024 at 7:24 PM Andy Shevchenko <andy@...nel.org> wrote:
> On Fri, Mar 01, 2024 at 02:42:03PM +1300, Chris Packham wrote:
> > Use the dot on the 7-segment LED block to indicate USB access on the
> > x530.
>
> As I said, I'm not going to apply this even with Acks.
I guess you should not apply any of the dts patches to the
auxdisplay tree anyway?
> The problem here as I see it is the future decision on how DP should
> behave like. If you put this into DT, we will to support this to the end
> of the platform.
As there exist 7-seg displays (and wirings) with and without DP,
the 7-seg driver and DT bindings should handle both cases. How to
wire/use the DP LED is up to the hardware designer / DTS writer.
I agree it's a thin boundary between hardware description and software
policy, though. Is that your main concern?
> So, drop this from the next version. You may try afterwards to apply it via
> different routes (will be not my problem :-).
Exactly ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68korg
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists