From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Pavel Machek <pavel@ucw.cz>, "lee@kernel.org" <lee@kernel.org>
Cc: "linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Linux support for a 7 segment LED display
Date: Sun, 11 Feb 2024 20:46:12 +0000 [thread overview]
Message-ID: <1f598a72-dd9f-4c6c-af7f-29751f84bd23@alliedtelesis.co.nz> (raw)
Hi Blinkenlight enthusiasts,
I'm looking for something that I figured must exists but maybe it's so
niche that no-one has bothered to upstream a driver for it.
I have a requirement to support a 7-segment LED display[1] (one that can
display a single digit from 0-9). Hardware wise it's just a bunch of
individual GPIOs connected to each segment (plus an extra one for a
dot). I can't see anything obvious in drivers/leds but maybe I'm looking
in the wrong place. Or maybe it's the kind of thing on PC hardware that
is just driven by the BIOS without the operating system knowing about it.
Is there an existing in-kernel driver for such a thing?
Thanks,
Chris
--
[1] - https://www.kingbrightusa.com/images/catalog/SPEC/SA36-11GWA.pdf
next reply other threads:[~2024-02-11 20:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 20:46 Chris Packham [this message]
2024-02-19 15:13 ` Linux support for a 7 segment LED display 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
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=1f598a72-dd9f-4c6c-af7f-29751f84bd23@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).