linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Lee Jones <lee@kernel.org>,
	linux-leds@vger.kernel.org, linux-pwm@vger.kernel.org,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [regression] stm32mp1xx based targets stopped entering suspend if pwm-leds exist
Date: Wed, 6 Mar 2024 08:05:15 +0100	[thread overview]
Message-ID: <5da6cf8a-4250-42f6-8b39-13bff7fcdd9c@leemhuis.info> (raw)

Hi, Thorsten here, the Linux kernel's regression tracker.

Uwe, I noticed a report about a regression in bugzilla.kernel.org that
apparently is caused by a change of yours. As many (most?) kernel
developers don't keep an eye on it, I decided to forward it by mail.

Note, you have to use bugzilla to reach the reporter, as I sadly[1] can
not CCed them in mails like this.

Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=218559 :

> Commit 76fe464c8e64e71b2e4af11edeef0e5d85eeb6aa ("leds: pwm: Don't
> disable the PWM when the LED should be off") prevents stm32mp1xx based
> targets from entering suspend if pwm-leds exist, as the stm32 PWM driver
> refuses to enter suspend if any PWM channels are still active ("PWM 0
> still in use by consumer" see stm32_pwm_suspend in drivers/pwm/stm32-pwm.c).
> 
> Reverting the mentioned commit fixes this behaviour but I'm not
> certain if this is a problem with stm32-pwm or pwm-leds (what is the
> usual behaviour for suspend with active PWM channels?).

See the ticket for more details.

[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar
form.]

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: 76fe464c8e64e71b
#regzbot duplicate https://bugzilla.kernel.org/show_bug.cgi?id=218559
#regzbot title: stm32mp1xx based targets stopped entering suspend if
pwm-leds exist
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

[1] because bugzilla.kernel.org tells users upon registration their
"email address will never be displayed to logged out users"

             reply	other threads:[~2024-03-06  7:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  7:05 Linux regression tracking (Thorsten Leemhuis) [this message]
2024-03-06  8:18 ` [regression] stm32mp1xx based targets stopped entering suspend if pwm-leds exist 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

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=5da6cf8a-4250-42f6-8b39-13bff7fcdd9c@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=lee@kernel.org \
    --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 NNTP newsgroup(s).