mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nam Tran <trannamatk@gmail.com>
To: andy@kernel.org
Cc: lee@kernel.org, geert@linux-m68k.org, pavel@ucw.cz,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	christophe.jaillet@wanadoo.fr, corbet@lwn.net,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, florian.fainelli@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 0/5] auxdisplay: add support for TI LP5812 4x3 Matrix LED driver
Date: Tue, 13 May 2025 00:38:00 +0700	[thread overview]
Message-ID: <20250512173800.6767-1-trannamatk@gmail.com> (raw)
In-Reply-To: <aCGPuKtfprIvwADa@smile.fi.intel.com>

On Mon, 12 May 2025 Andy Shevchenko wrote:

> On Sat, May 10, 2025 at 02:48:02PM +0700, Nam Tran wrote:
> > On Thu, 8 May 2025 Lee Jones wrote:
> > > On Thu, 08 May 2025, Andy Shevchenko wrote:
> > > > On Thu, May 8, 2025 at 5:27 PM Nam Tran <trannamatk@gmail.com> wrote:
> > > > > On Thu, 8 May 2025 Lee Jones wrote:
> > > > > > On Thu, 08 May 2025, Andy Shevchenko wrote:

...

> > I think setting PWM also same as brightness_set API. However, there are
> > many PWM config for a LED and it is one of other config to make autonomous mode work.
> > Therefore, standard led API can use in some use cases only.
> > 
> > Please see the link below for a better visualization of how to configure the LP5812.
> > https://dev.ti.com/gallery/view/LED/LP581x/ver/0.10.0/
> 
> To me it sounds like you should start from the small steps, i.e. do not
> implement everything at once. And starting point of the 4 RGB LEDs sounds
> the best approach to me. Then, if needed, you can always move on with
> fancy features of this hardware on top of the existing code.

Thanks for the suggestion.
I understand your point and agree that starting with standard LED APIs is the preferred approach.

However, the LP5812 hardware offers more advanced features, and I’d like to support end users all
features as shown in the link: https://dev.ti.com/gallery/view/LED/LP581x/ver/0.10.0/.
It is easy for end user to investigate and use driver.

If I want to keep the current driver interface to meet this expectation, would it be acceptable
to move it to the misc subsystem to better support the hardware?

Best regards,
Nam Tran

  reply	other threads:[~2025-05-12 17:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-27  8:24 Nam Tran
2025-04-27  8:24 ` [PATCH v8 1/5] dt-bindings: auxdisplay: add TI LP5812 4×3 Matrix RGB LED Driver Nam Tran
2025-04-27  8:24 ` [PATCH v8 2/5] " Nam Tran
2025-04-27 16:04   ` Randy Dunlap
2025-04-28 17:39     ` Nam Tran
2025-04-27  8:24 ` [PATCH v8 3/5] docs: ABI: Document LP5812 sysfs interfaces Nam Tran
2025-04-27  8:24 ` [PATCH v8 4/5] docs: auxdisplay: document TI LP5812 RGB LED driver Nam Tran
2025-04-27  8:24 ` [PATCH v8 5/5] arm64: dts: Add LP5812 node for Raspberry Pi 4 Model B Nam Tran
2025-04-27  9:35 ` [PATCH v8 0/5] auxdisplay: add support for TI LP5812 4x3 Matrix LED driver Andy Shevchenko
2025-04-28 10:37   ` Pavel Machek
2025-04-28 11:34     ` Geert Uytterhoeven
2025-04-28 17:29       ` Nam Tran
2025-04-28 20:18         ` Pavel Machek
2025-04-29 17:02           ` Nam Tran
2025-04-29 19:47             ` Andy Shevchenko
2025-05-07 16:42               ` Nam Tran
2025-05-08  8:24                 ` Andy Shevchenko
2025-05-08 13:26                   ` Lee Jones
2025-05-08 14:26                     ` Nam Tran
2025-05-08 14:46                       ` Andy Shevchenko
2025-05-08 15:01                         ` Lee Jones
2025-05-10  7:48                           ` Nam Tran
2025-05-12  6:05                             ` Andy Shevchenko
2025-05-12 17:38                               ` Nam Tran [this message]
2025-05-12 17:44                                 ` Andy Shevchenko
2025-05-13  8:35                                   ` Lee Jones
2025-05-13  8:10                                 ` Geert Uytterhoeven
2025-05-13  8:50                                   ` Lee Jones
2025-04-30  7:15             ` Pavel Machek
2025-05-05  7:24               ` Nam Tran
2025-05-08  8:38             ` Pavel Machek
2025-04-28 16:37   ` Nam Tran

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=20250512173800.6767-1-trannamatk@gmail.com \
    --to=trannamatk@gmail.com \
    --cc=andy@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=geert@linux-m68k.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=pavel@ucw.cz \
    --cc=robh@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

all inboxes | Powered by JetHome®