Message ID | 20210625125902.1162428-1-geert@linux-m68k.org |
---|---|
Headers | show |
Series | auxdisplay: ht16k33: Add character display support | expand |
On Fri, 25 Jun 2021 22:39:16 +0200 Marek Behun <marek.behun@nic.cz> wrote: > On Fri, 25 Jun 2021 14:59:02 +0200 > Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > > Instantiate a single LED for a segment display. This allows the user to > > control display brightness and blinking through the LED class API and > > triggers, and exposes the display color. > > The LED will be named "auxdisplay:<color>:backlight". > > What if there are multiple "auxdisplay"s ? > Doesn't this subsystem have IDs? So that you can use auxdisplayN for > device name, for example? Or if this driver creates a fbdev, maybe "fb<N>" for devicename? Marek
Hi Marek, On Fri, Jun 25, 2021 at 10:40 PM Marek Behun <marek.behun@nic.cz> wrote: > On Fri, 25 Jun 2021 22:39:16 +0200 > Marek Behun <marek.behun@nic.cz> wrote: > > On Fri, 25 Jun 2021 14:59:02 +0200 > > Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > > Instantiate a single LED for a segment display. This allows the user to > > > control display brightness and blinking through the LED class API and > > > triggers, and exposes the display color. > > > The LED will be named "auxdisplay:<color>:backlight". > > > > What if there are multiple "auxdisplay"s ? > > Doesn't this subsystem have IDs? So that you can use auxdisplayN for > > device name, for example? > > Or if this driver creates a fbdev, maybe "fb<N>" for devicename? This LED device is only registered when using the HT16K33 to drive segment displays. When driving a dot matrix display, the driver still use fbdev and devm_backlight_device_register(), for backwards compatibility. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org 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