mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: "Uwe Kleine-König" <ukleinek@kernel.org>,
	"Jonathan Hunter" <jonathanh@nvidia.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	linux-pwm@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pwm: tegra: fail probe on reset deassert errors
Date: Fri, 11 Sep 2026 12:43:57 +0200	[thread overview]
Message-ID: <aqPaVTsO9ZvB1F_O@orome> (raw)
In-Reply-To: <20260830125843.99132-1-pengpeng@iscas.ac.cn>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

On Sun, Aug 30, 2026 at 08:58:43PM +0800, Pengpeng Hou wrote:
> tegra_pwm_probe() registers the PWM provider after deasserting the reset
> control without checking whether the reset controller accepted the request.
> 
> Propagate the failure through the existing runtime-PM cleanup path instead
> of publishing a PWM controller whose hardware may still be reset.
> 
> Fixes: 5dfbd2bd5439 ("pwm: tegra: Add support for reset control")
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
> ---
>  drivers/pwm/pwm-tegra.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)

This is probably purely cosmetic since I've never seen a reset fail to
assert or deassert on Tegra (old generations can only fail if the reset
ID is invalid, meaning it's a bug in the framework, and new generations
may fail if for some reason the BPMP is not operational, in which case
the boot will fail much earlier).

Anyway, not saying NAK because from an API point of view it's correct to
check this. However, the Fixes: tag is a bit overkill. This does not
need to be backported to 10 years' worth of stable kernels.

Acked-by: Thierry Reding <treding@nvidia.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2026-09-11 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-30 12:58 Pengpeng Hou
2026-09-10 14:34 ` Uwe Kleine-König
2026-09-11 10:43 ` Thierry Reding [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=aqPaVTsO9ZvB1F_O@orome \
    --to=thierry.reding@kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=pengpeng@iscas.ac.cn \
    --cc=ukleinek@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®