From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: andy@kernel.org, geert@linux-m68k.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
andrew@lunn.ch, gregory.clement@bootlin.com,
sebastian.hesselbarth@gmail.com, pavel@ucw.cz, lee@kernel.org
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v3 0/4] auxdisplay: 7 segment LED display
Date: Fri, 1 Mar 2024 14:41:59 +1300 [thread overview]
Message-ID: <20240301014203.2033844-1-chris.packham@alliedtelesis.co.nz> (raw)
This series adds a driver for a 7 segment LED display.
I haven't had a chance to look at the gpio changes that'd be required to
have multiple characters as subnodes. I wanted to get the code that
addressed Andy and Rob's comments out before my weekend.
--
[1] - https://lore.kernel.org/lkml/2a8d19ee-b18b-4b7c-869f-7d601cea30b6@alliedtelesis.co.nz/
Chris Packham (4):
auxdisplay: Add 7-segment LED display driver
dt-bindings: auxdisplay: Add bindings for generic 7-segment LED
ARM: dts: marvell: Add 7-segment LED display on x530
ARM: dts: marvell: Indicate USB activity on x530
.../bindings/auxdisplay/gpio-7-segment.yaml | 42 ++++++
.../boot/dts/marvell/armada-385-atl-x530.dts | 22 +++-
drivers/auxdisplay/Kconfig | 10 ++
drivers/auxdisplay/Makefile | 1 +
drivers/auxdisplay/seg-led-gpio.c | 122 ++++++++++++++++++
5 files changed, 196 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/auxdisplay/gpio-7-segment.yaml
create mode 100644 drivers/auxdisplay/seg-led-gpio.c
--
2.43.2
next reply other threads:[~2024-03-01 1:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 1:41 Chris Packham [this message]
2024-03-01 1:42 ` [PATCH v3 1/4] auxdisplay: Add 7-segment LED display driver Chris Packham
2024-03-01 18:18 ` Andy Shevchenko
2024-03-03 19:58 ` Chris Packham
2024-03-03 20:35 ` Andy Shevchenko
2024-03-03 20:56 ` Yury Norov
2024-03-04 0:45 ` Chris Packham
2024-03-04 0:46 ` Chris Packham
2024-03-01 1:42 ` [PATCH v3 2/4] dt-bindings: auxdisplay: Add bindings for generic 7-segment LED Chris Packham
2024-03-01 18:21 ` Andy Shevchenko
2024-03-01 1:42 ` [PATCH v3 3/4] ARM: dts: marvell: Add 7-segment LED display on x530 Chris Packham
2024-03-01 18:22 ` Andy Shevchenko
2024-03-01 1:42 ` [PATCH v3 4/4] ARM: dts: marvell: Indicate USB activity " Chris Packham
2024-03-01 18:24 ` Andy Shevchenko
2024-03-03 9:48 ` Geert Uytterhoeven
2024-03-03 20:11 ` Chris Packham
2024-03-03 20:43 ` Andy Shevchenko
2024-03-04 9:57 ` Geert Uytterhoeven
2024-03-04 18:17 ` Andy Shevchenko
2024-03-04 19:01 ` Geert Uytterhoeven
2024-03-04 19:16 ` Andy Shevchenko
2024-03-01 18:31 ` [PATCH v3 0/4] auxdisplay: 7 segment LED display Andy Shevchenko
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=20240301014203.2033844-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
/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 NNTP newsgroup(s).