All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jean-Francois Lessard <jefflessard3@gmail.com>
Cc: devicetree@vger.kernel.org, andy@kernel.org, geert@linux-m68k.org
Subject: Re: [RFC][DT] Guidance on device tree property prefix for TM16XX-class LED display controllers
Date: Mon, 16 Jun 2025 20:02:51 +0300	[thread overview]
Message-ID: <aFBOO1LtLRagMGMz@smile.fi.intel.com> (raw)
In-Reply-To: <CADsqogD=zfC--XHhSXZ=cDHZ3TMNpcU2WUS0stY2HhuRNdzPXg@mail.gmail.com>

On Mon, Jun 16, 2025 at 12:05:11PM -0400, Jean-Francois Lessard wrote:
> Hi all,
> 
> I’m working on preparing a new driver and device tree binding for auxiliary
> LED display controllers of the TM16XX class, and I’d like to request
> guidance on property naming conventions before submitting a formal patch
> series.

> The driver (tentatively named tm16xx) supports LED controller chips that
> share a common hardware design and programming model, produced by multiple
> vendors, including:
> 
> Titan Micro Electronics: TM1618, TM1620, TM1628, TM1650
> 
> FUDA HISI Microelectronics: FD620, FD628, FD650, FD655, FD6551
> 
> Princeton Technology Corp: PT6964
> 
> HBS: HBS658
> 
> tm16xx,digits = /bits/ 8 <0 1 2 3>;
> tm16xx,segment-mapping = /bits/ 8 <0 1 2 3 4 5 6>;
> tm16xx,transposed;

I'm not sure I got what the controller is. Is it for 7-segment like display or
is it something else?

Because it might be that LED subsystem is not the best for it to begin with.

-- 
With Best Regards,
Andy Shevchenko



       reply	other threads:[~2025-06-16 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADsqogD=zfC--XHhSXZ=cDHZ3TMNpcU2WUS0stY2HhuRNdzPXg@mail.gmail.com>
2025-06-16 17:02 ` Andy Shevchenko [this message]
2025-06-16 20:06 [RFC][DT] Guidance on device tree property prefix for TM16XX-class LED display controllers Jean-Francois Lessard
2025-06-16 20:26 ` Andy Shevchenko
2025-06-16 23:07   ` Jean-Francois Lessard
2025-06-17  9:43 ` Geert Uytterhoeven
2025-06-17 11:57   ` Andy Shevchenko
2025-06-17 13:39     ` Jean-Francois Lessard
2025-06-17 18:40       ` Andy Shevchenko
2025-06-18 18:30         ` Jean-Francois Lessard

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=aFBOO1LtLRagMGMz@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=jefflessard3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.