From: Lee Jones <lee@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
linux-leds@vger.kernel.org, linux-pwm@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
kernel@pengutronix.de
Subject: Re: (subset) [PATCH] leds: pwm: Disable PWM when going to suspend
Date: Thu, 2 May 2024 18:04:41 +0100 [thread overview]
Message-ID: <20240502170441.GD1200070@google.com> (raw)
In-Reply-To: <171466932928.1214296.17132644352212078458.b4-ty@kernel.org>
On Thu, 02 May 2024, Lee Jones wrote:
> On Wed, 17 Apr 2024 17:38:47 +0200, Uwe Kleine-König wrote:
> > On stm32mp1xx based machines (and others) a PWM consumer has to disable
> > the PWM because an enabled PWM refuses to suspend. So check the
> > LED_SUSPENDED flag and depending on that set the .enabled property.
> >
> >
>
> Applied, thanks!
>
> [1/1] leds: pwm: Disable PWM when going to suspend
> commit: 974afccd37947a6951a052ef8118c961e57eaf7b
If this is important, you may wish to retroactively send it to Stable
once it's been merged into Mainline.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-05-02 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 7:05 [regression] stm32mp1xx based targets stopped entering suspend if pwm-leds exist Linux regression tracking (Thorsten Leemhuis)
2024-03-06 8:18 ` Uwe Kleine-König
2024-04-16 8:28 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-16 12:15 ` Lee Jones
2024-04-16 13:18 ` Uwe Kleine-König
2024-04-17 14:49 ` Lee Jones
2024-04-17 15:38 ` [PATCH] leds: pwm: Disable PWM when going to suspend Uwe Kleine-König
2024-04-26 6:17 ` Uwe Kleine-König
2024-04-26 6:30 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-02 17:02 ` (subset) " Lee Jones
2024-05-02 17:04 ` Lee Jones [this message]
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=20240502170441.GD1200070@google.com \
--to=lee@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=u.kleine-koenig@pengutronix.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).