From: Heiner Kallweit <hkallweit1@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
"Andreas Färber" <afaerber@suse.de>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Kevin Hilman" <khilman@baylibre.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>
Subject: Re: [PATCH v2 5/6] auxdisplay: add support for Titanmec TM1628 7 segment display controller
Date: Tue, 22 Feb 2022 10:44:45 +0100 [thread overview]
Message-ID: <288225b9-85e0-0c46-5d8b-c91f76c796e5@gmail.com> (raw)
In-Reply-To: <CAMuHMdUnDQKtGuN+n-t3P8e4nf9VLB+9q8fGyCh643T4Y1Knag@mail.gmail.com>
On 22.02.2022 09:19, Geert Uytterhoeven wrote:
> Hi Heiner,
>
> On Mon, Feb 21, 2022 at 9:26 PM Heiner Kallweit <hkallweit1@gmail.com> wrote:
>> This patch adds support for the Titanmec TM1628 7 segment display
>> controller. It's based on previous RFC work from Andreas Färber.
>> The RFC version placed the driver in the LED subsystem, but this was
>> NAK'ed by the LED maintainer. Therefore I moved the driver to
>> /drivers/auxdisplay what seems most reasonable to me.
>>
>> Further changes to the RFC version:
>> - Driver can be built also w/o LED class support, for displays that
>> don't have any symbols to be exposed as LED's.
>> - Simplified the code and rewrote a lot of it.
>> - Driver is now kind of a MVP, but functionality should be sufficient
>> for most use cases.
>> - Use the existing 7 segment support in uapi/linux/map_to_7segment.h
>> as suggested by Geert Uytterhoeven.
>>
>> Note: There's a number of chips from other manufacturers that are
>> almost identical, e.g. FD628, SM1628. Only difference I saw so
>> far is that they partially support other display modes.
>> TM1628: 6x12, 7x11
>> SM1628C: 4x13, 5x12, 6x11, 7x10
>> For typical displays on devices using these chips this
>> difference shouldn't matter.
>>
>> Successfully tested on a TX3 Mini TV box that has an SM1628C and a
>> display with 4 digits and 7 symbols.
>>
>> Tested-by: Christian Hewitt <christianshewitt@gmail.com>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>
> Thanks for your patch!
>
>> --- /dev/null
>> +++ b/drivers/auxdisplay/tm1628.c
>
>> +static int tm1628_show_text(struct tm1628 *s)
>> +{
>> + static SEG7_CONVERSION_MAP(map_seg7, MAP_ASCII7SEG_ALPHANUM);
>
> This mapping can not be overridden by the user. Is there any
> specific reason you didn't make the mapping configurable from sysfs,
> cfr. map_seg7_{show,store}() in include/uapi/linux/map_to_7segment.h?
>
The more features an initial driver version includes, the more discussion
topics pop up and make it less likely that we end up with at least something.
I think there's a reason why the driver was resting since the initial
attempt 2 yrs ago. Therefore I'd like to keep it as a MVP.
If somebody should have the need for add-on features, then they can be
added later.
> Gr{oetje,eeting}s,
>
> Geert
>
Heiner
> --
> 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
next prev parent reply other threads:[~2022-02-22 9:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 20:19 [PATCH v2 0/6] auxdisplay: Add support for the Titanmec TM1628 7 segment display controller Heiner Kallweit
2022-02-21 20:20 ` [PATCH v2 1/6] spi: gpio: Implement LSB First bitbang support Heiner Kallweit
2022-02-21 20:21 ` [PATCH v2 2/6] dt-bindings: vendor-prefixes: Add Titan Micro Electronics Heiner Kallweit
2022-02-21 20:23 ` [PATCH v2 3/6] dt-bindings: auxdisplay: Add Titan Micro Electronics TM1628 Heiner Kallweit
2022-02-22 14:22 ` Rob Herring
2022-02-21 20:24 ` [PATCH v2 4/6] docs: ABI: document tm1628 attribute display-text Heiner Kallweit
2022-02-22 8:20 ` Geert Uytterhoeven
2022-02-21 20:25 ` [PATCH v2 5/6] auxdisplay: add support for Titanmec TM1628 7 segment display controller Heiner Kallweit
2022-02-22 8:19 ` Geert Uytterhoeven
2022-02-22 9:44 ` Heiner Kallweit [this message]
2022-02-22 12:16 ` Andreas Färber
2022-02-22 13:39 ` Heiner Kallweit
2022-02-21 20:26 ` [PATCH v2 6/6] arm64: dts: meson-gxl-s905w-tx3-mini: add support for the 7 segment display Heiner Kallweit
2022-02-21 22:10 ` [PATCH v2 0/6] auxdisplay: Add support for the Titanmec TM1628 7 segment display controller Miguel Ojeda
2022-02-21 22:57 ` Heiner Kallweit
2022-02-22 12:19 ` Andreas Färber
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=288225b9-85e0-0c46-5d8b-c91f76c796e5@gmail.com \
--to=hkallweit1@gmail.com \
--cc=afaerber@suse.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=ojeda@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).