From: Lee Jones <lee@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Jakob Riepler <jakob+lkml@paranoidlabs.org>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v4] leds: pwm-multicolor: Disable PWM when going to suspend
Date: Thu, 19 Dec 2024 08:25:04 +0000 [thread overview]
Message-ID: <20241219082504.GM2418536@google.com> (raw)
In-Reply-To: <kfkfwwv3ytv3jdcfg5xle6xjks7mjk6ziqe75lrhq4tqfgi6pk@borrphl7vatz>
On Thu, 19 Dec 2024, Uwe Kleine-König wrote:
> Hello Lee,
>
> On Tue, Dec 17, 2024 at 03:05:06PM +0000, Lee Jones wrote:
> > On Mon, 16 Dec 2024 22:37:55 +0100, Jakob Riepler wrote:
> > > This fixes suspend on platforms like stm32mp1xx, where the PWM consumer
> > > has to be disabled for the PWM to enter suspend.
> > > Another positive side effect is that active-low LEDs now properly
> > > turn off instead of going back to full brightness when they are set to 0.
> > >
> > >
> >
> > Applied, thanks!
> >
> > [1/1] leds: pwm-multicolor: Disable PWM when going to suspend
> > commit: 29df7025cff00dd9fa7cacbec979ede97ee775eb
>
> Where is this applied? I checked today's next and even after
>
> for b in for-leds-next for-leds-next-next leds-fixes master; do git fetch git://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git refs/heads/$b; done
>
> I don't have the above commit object and these branches don't seem to
> contain the commit with a different commit id either.
Check again tomorrow. :)
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-12-19 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 21:37 [PATCH v4] leds: pwm-multicolor: Disable PWM when going to suspend Jakob Riepler
2024-12-17 8:55 ` Uwe Kleine-König
2024-12-17 15:05 ` (subset) " Lee Jones
2024-12-19 8:11 ` Uwe Kleine-König
2024-12-19 8:25 ` Lee Jones [this message]
2024-12-19 13:49 ` Uwe Kleine-König
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=20241219082504.GM2418536@google.com \
--to=lee@kernel.org \
--cc=jakob+lkml@paranoidlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=u.kleine-koenig@baylibre.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.