From: Pavel Machek <pavel@ucw.cz>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"lee@kernel.org" <lee@kernel.org>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux support for a 7 segment LED display
Date: Thu, 22 Feb 2024 23:34:40 +0100 [thread overview]
Message-ID: <ZdfMAP5Z7fiKHtSf@duo.ucw.cz> (raw)
In-Reply-To: <9d00e1b1-120b-4c2b-89c5-0ac736bf6441@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
Hi!
> > Cc: Geert and Krzysztof (for the comments on the idea above).
>
> Would the gpio-aggregator be necessary? I was thinking something like
> this in the devicetree
>
> \{
> led-7seg {
> compatible = "kingbright,sa36";
Please make it something like "generic,7-segment-on-gpio". I assume
there's a ton of similar display units.
BR,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2024-02-22 22:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 20:46 Linux support for a 7 segment LED display Chris Packham
2024-02-19 15:13 ` Lee Jones
2024-02-19 20:12 ` Chris Packham
2024-02-20 8:18 ` Lee Jones
2024-02-20 17:30 ` Pavel Machek
2024-02-19 15:34 ` Pavel Machek
2024-02-19 20:08 ` Chris Packham
2024-02-22 21:34 ` andy.shevchenko
2024-02-22 21:53 ` Chris Packham
2024-02-22 21:59 ` Andy Shevchenko
2024-02-22 22:08 ` Chris Packham
2024-02-22 22:13 ` Andy Shevchenko
2024-02-23 3:46 ` Chris Packham
2024-02-23 7:47 ` Pavel Machek
2024-02-23 7:53 ` Geert Uytterhoeven
2024-02-23 7:51 ` Geert Uytterhoeven
2024-02-23 12:35 ` Andy Shevchenko
2024-02-23 13:01 ` Geert Uytterhoeven
2024-02-23 14:44 ` Andy Shevchenko
2024-02-22 22:34 ` Pavel Machek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZdfMAP5Z7fiKHtSf@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=andy.shevchenko@gmail.com \
--cc=geert@linux-m68k.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox