[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nUkMj5bg8CDAg-2G0wdAjAe2CdHL5mb2cwWXF_d4Qgtw@mail.gmail.com>
Date: Wed, 15 Jan 2020 15:31:34 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Andreas Färber <afaerber@...e.de>
Cc: Dan Murphy <dmurphy@...com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Pavel Machek <pavel@....cz>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-leds@...r.kernel.org, linux-realtek-soc@...ts.infradead.org
Subject: Re: [RFC 22/25] leds: tm1826: Add combined glyph support
Hi Andreas,
On Sun, Dec 22, 2019 at 4:14 AM Andreas Färber <afaerber@...e.de> wrote:
>
> Please find the full series on, e.g., LAKML:
>
> https://patchwork.kernel.org/cover/11286939/
Sorry for the late reply. Thanks for the pointer!
> As explained in the cover letter, the problem here is that I don't know
> the model or manufacturer of these unmarked white-plastic-frame LED
> displays. So we have neither a filename to use in auxdisplay/ nor a DT
> compatible string to use for those displays.
For the filename, I don't think it is a big deal. Just use whatever
you think would fit best, even if it is a generic name. The most
important bit is having a clear Kconfig (and being disabled by
default).
Cheers,
Miguel
Powered by blists - more mailing lists