Linux LED subsystem development
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "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: Mon, 19 Feb 2024 16:34:51 +0100	[thread overview]
Message-ID: <ZdN1G6PfCK9/vUol@duo.ucw.cz> (raw)
In-Reply-To: <1f598a72-dd9f-4c6c-af7f-29751f84bd23@alliedtelesis.co.nz>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

Hi!

> 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.

Look at drivers/auxdisplay. I believe we have segment displays there.

Best regards,
								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2024-02-19 15: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 [this message]
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=ZdN1G6PfCK9/vUol@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --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