From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Mikko Perttunen <mperttunen@nvidia.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-pwm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Yi-Wei Wang <yiweiw@nvidia.com>
Subject: Re: [PATCH v4 4/7] pwm: tegra: Parametrize enable register offset
Date: Sun, 17 May 2026 19:35:35 +0200 [thread overview]
Message-ID: <agn7SP3ETY4XCX4h@monoceros> (raw)
In-Reply-To: <20260331-t264-pwm-v4-4-c041659677cf@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 3142 bytes --]
Hello,
On Tue, Mar 31, 2026 at 11:12:16AM +0900, Mikko Perttunen wrote:
> On Tegra264, the PWM enablement bit is not located at the base address
> of the PWM controller. Hence, introduce an enablement offset field in
> the tegra_pwm_soc structure to describe the offset of the register.
>
> Co-developed-by: Yi-Wei Wang <yiweiw@nvidia.com>
> Signed-off-by: Yi-Wei Wang <yiweiw@nvidia.com>
> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> ---
> drivers/pwm/pwm-tegra.c | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c
> index 358c81cea05b..b925ef914411 100644
> --- a/drivers/pwm/pwm-tegra.c
> +++ b/drivers/pwm/pwm-tegra.c
> @@ -61,6 +61,7 @@
>
> struct tegra_pwm_soc {
> unsigned int num_channels;
> + unsigned int enable_reg;
> };
>
> struct tegra_pwm_chip {
> @@ -197,8 +198,9 @@ static int tegra_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
> err = pm_runtime_resume_and_get(pwmchip_parent(chip));
> if (err)
> return err;
> - } else
> + } else if (pc->soc->enable_reg == PWM_CSR_0) {
> val |= PWM_ENABLE;
> + }
>
> pwm_writel(pwm, PWM_CSR_0, val);
>
The patch is a bit artificial because we don't have a driver yet where
`pc->soc->enable_reg == PWM_CSR_0` doesn't hold. But it looks strange to
me that there is no enable bit set for the pc->soc->enable_reg !=
PWM_CSR_0 case. So I tend to want these changes in squashed into another
patch such that the combined patch handles the enabling completely.
> @@ -213,6 +215,7 @@ static int tegra_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
>
> static int tegra_pwm_enable(struct pwm_chip *chip, struct pwm_device *pwm)
> {
> + struct tegra_pwm_chip *pc = to_tegra_pwm_chip(chip);
> int rc = 0;
> u32 val;
>
> @@ -220,20 +223,22 @@ static int tegra_pwm_enable(struct pwm_chip *chip, struct pwm_device *pwm)
> if (rc)
> return rc;
>
> - val = pwm_readl(pwm, PWM_CSR_0);
> +
A single empty line is enough.
> + val = pwm_readl(pwm, pc->soc->enable_reg);
> val |= PWM_ENABLE;
> - pwm_writel(pwm, PWM_CSR_0, val);
> + pwm_writel(pwm, pc->soc->enable_reg, val);
>
> return 0;
> }
>
> static void tegra_pwm_disable(struct pwm_chip *chip, struct pwm_device *pwm)
> {
> + struct tegra_pwm_chip *pc = to_tegra_pwm_chip(chip);
> u32 val;
>
> - val = pwm_readl(pwm, PWM_CSR_0);
> + val = pwm_readl(pwm, pc->soc->enable_reg);
> val &= ~PWM_ENABLE;
> - pwm_writel(pwm, PWM_CSR_0, val);
> + pwm_writel(pwm, pc->soc->enable_reg, val);
>
> pm_runtime_put_sync(pwmchip_parent(chip));
> }
> @@ -398,10 +403,12 @@ static int __maybe_unused tegra_pwm_runtime_resume(struct device *dev)
>
> static const struct tegra_pwm_soc tegra20_pwm_soc = {
> .num_channels = 4,
> + .enable_reg = PWM_CSR_0,
> };
>
> static const struct tegra_pwm_soc tegra186_pwm_soc = {
> .num_channels = 1,
> + .enable_reg = PWM_CSR_0,
> };
>
> static const struct of_device_id tegra_pwm_of_match[] = {
>
> --
> 2.53.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-05-17 17:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 2:12 [PATCH v4 0/7] Tegra264 PWM support Mikko Perttunen
2026-03-31 2:12 ` [PATCH v4 1/7] dt-bindings: pwm: Document Tegra264 controller Mikko Perttunen
2026-04-08 13:27 ` Rob Herring (Arm)
2026-03-31 2:12 ` [PATCH v4 2/7] pwm: tegra: Avoid hard-coded max clock frequency Mikko Perttunen
2026-03-31 7:29 ` Thierry Reding
2026-03-31 2:12 ` [PATCH v4 3/7] pwm: tegra: Modify read/write accessors for multi-register channel Mikko Perttunen
2026-05-17 17:30 ` Uwe Kleine-König
2026-05-18 2:31 ` Mikko Perttunen
2026-03-31 2:12 ` [PATCH v4 4/7] pwm: tegra: Parametrize enable register offset Mikko Perttunen
2026-03-31 7:30 ` Thierry Reding
2026-05-17 17:35 ` Uwe Kleine-König [this message]
2026-05-18 2:30 ` Mikko Perttunen
2026-03-31 2:12 ` [PATCH v4 5/7] pwm: tegra: Parametrize duty and scale field widths Mikko Perttunen
2026-03-31 2:12 ` [PATCH v4 6/7] pwm: tegra: Add support for Tegra264 Mikko Perttunen
2026-03-31 7:36 ` Thierry Reding
2026-03-31 2:12 ` [PATCH v4 7/7] arm64: tegra: Add PWM controllers on Tegra264 Mikko Perttunen
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=agn7SP3ETY4XCX4h@monoceros \
--to=ukleinek@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=yiweiw@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox