U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Marangi <ansuelsmth@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	Doug Zobel <douglas.zobel@climate.com>,
	Marek Vasut <marex@denx.de>,
	Christian Gmeiner <christian.gmeiner@gmail.com>,
	u-boot@lists.denx.de,
	Michael Polyntsov <michael.polyntsov@iopsys.eu>
Subject: Re: [PATCH 1/2] led: Implement software led blinking
Date: Thu, 27 Jun 2024 22:29:13 +0200	[thread overview]
Message-ID: <667dcb97.050a0220.98d34.34cd@mx.google.com> (raw)
In-Reply-To: <20240627193609.GF38804@bill-the-cat>

On Thu, Jun 27, 2024 at 01:36:09PM -0600, Tom Rini wrote:
> On Thu, Jun 27, 2024 at 02:31:13PM +0300, Mikhail Kshevetskiy wrote:
> 
> > From: Michael Polyntsov <michael.polyntsov@iopsys.eu>
> > 
> > If hardware (or driver) doesn't support leds blinking, it's
> > now possible to use software implementation of blinking instead.
> > This relies on cyclic functions.
> > 
> > Signed-off-by: Michael Polyntsov <michael.polyntsov@iopsys.eu>
> > Signed-off-by: Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>
> > ---
> >  drivers/led/Kconfig      |   9 ++
> >  drivers/led/led-uclass.c | 190 ++++++++++++++++++++++++++++++++++++++-
> >  2 files changed, 195 insertions(+), 4 deletions(-)
> 
> As one of those "well, hunh" kind of moment, I'm cc'ing Christian
> Marangi who also just posted patches foor this kind of functionality.
> 

Eh... Well this implementation is better. I had the idea of adding
support on the uclass level but I preferred to limit it only to GPIO.

Think this would match how it's done in upstream linux kernel so I think
mine should be ignored and this taken (for sw blink).

Should not change a thing for the series since all the bits were using
generic LED functions.

-- 
	Ansuel

  reply	other threads:[~2024-06-27 20:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 11:31 [PATCH 1/2] led: Implement software led blinking Mikhail Kshevetskiy
2024-06-27 11:31 ` [PATCH 2/2] led: Add dts property to specify blinking of the led Mikhail Kshevetskiy
2024-06-27 19:05 ` [PATCH 1/2] led: Implement software led blinking Simon Glass
2024-07-02 11:54   ` Mikhail Kshevetskiy
2024-07-02 15:51     ` Simon Glass
2024-07-03  1:01       ` led blinking patches Mikhail Kshevetskiy
2024-07-03  1:01         ` [PATCH 1/2] led: Implement software led blinking Mikhail Kshevetskiy
2024-07-03  8:08           ` Simon Glass
2024-07-03 11:27           ` Rasmus Villemoes
2024-07-03  1:01         ` [PATCH 2/2] led: Add dts property to specify blinking of the led Mikhail Kshevetskiy
2024-07-03  8:08           ` Simon Glass
2024-07-05  2:20             ` Mikhail Kshevetskiy
2024-06-27 19:36 ` [PATCH 1/2] led: Implement software led blinking Tom Rini
2024-06-27 20:29   ` Christian Marangi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-05  2:26 Mikhail Kshevetskiy
2024-07-05  8:29 ` Mark Kettenis
2024-07-05  9:24   ` Mikhail Kshevetskiy

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=667dcb97.050a0220.98d34.34cd@mx.google.com \
    --to=ansuelsmth@gmail.com \
    --cc=christian.gmeiner@gmail.com \
    --cc=douglas.zobel@climate.com \
    --cc=marex@denx.de \
    --cc=michael.polyntsov@iopsys.eu \
    --cc=mikhail.kshevetskiy@iopsys.eu \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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