Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1634441 > unrolled thread

[PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout

Started byLaxman Dewangan <ldewangan@nvidia.com>
First post2017-05-02 16:10 +0200
Last post2017-05-02 22:20 +0200
Articles 4 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout Laxman Dewangan <ldewangan@nvidia.com> - 2017-05-02 16:10 +0200
    Re: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC  tapeout Jon Hunter <jonathanh@nvidia.com> - 2017-05-02 17:30 +0200
      Re: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout Laxman Dewangan <ldewangan@nvidia.com> - 2017-05-02 19:50 +0200
        Re: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC  tapeout Jon Hunter <jonathanh@nvidia.com> - 2017-05-02 22:20 +0200

#1634441 — [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout

FromLaxman Dewangan <ldewangan@nvidia.com>
Date2017-05-02 16:10 +0200
Subject[PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout
Message-ID<tCGF3-7GU-15@gated-at.bofh.it>
The PWM hardware IP is taped-out with different maximum frequency
on different SoCs.

From HW team:
	Before Tegra186, it is 38.4MHz.
	In Tegra186, it is 102MHz.

Add support to limit the clock source frequency to the maximum IP
supported frequency. Provide these values via SoC chipdata.

Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>

---
Changes from V1:
- Set the 48MHz maximum frequency for Tegra210 and earlier.
- Set the maximum frequency unconditionally as per V1 review comment.
---
 drivers/pwm/pwm-tegra.c | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c
index 8c6ed55..e9b33f0 100644
--- a/drivers/pwm/pwm-tegra.c
+++ b/drivers/pwm/pwm-tegra.c
@@ -41,6 +41,9 @@
 
 struct tegra_pwm_soc {
 	unsigned int num_channels;
+
+	/* Maximum IP frequency for given SoCs */
+	unsigned long max_frequency;
 };
 
 struct tegra_pwm_chip {
@@ -201,7 +204,18 @@ static int tegra_pwm_probe(struct platform_device *pdev)
 	if (IS_ERR(pwm->clk))
 		return PTR_ERR(pwm->clk);
 
-	/* Read PWM clock rate from source */
+	/* Set maximum frequency of the IP */
+	ret = clk_set_rate(pwm->clk, pwm->soc->max_frequency);
+	if (ret < 0) {
+		dev_err(&pdev->dev, "Failed to set max frequency: %d\n", ret);
+		return ret;
+	}
+
+	/*
+	 * The requested and configured frequency may differ due to
+	 * clock register resolutions. Get the configured frequency
+	 * so that PWM period can be calculated more accurately.
+	 */
 	pwm->clk_rate = clk_get_rate(pwm->clk);
 
 	pwm->rst = devm_reset_control_get(&pdev->dev, "pwm");
@@ -273,10 +287,12 @@ static int tegra_pwm_resume(struct device *dev)
 
 static const struct tegra_pwm_soc tegra20_pwm_soc = {
 	.num_channels = 4,
+	.max_frequency = 48000000UL,
 };
 
 static const struct tegra_pwm_soc tegra186_pwm_soc = {
 	.num_channels = 1,
+	.max_frequency = 102000000UL,
 };
 
 static const struct of_device_id tegra_pwm_of_match[] = {
-- 
2.1.4

[toc] | [next] | [standalone]


#1634482 — Re: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout

FromJon Hunter <jonathanh@nvidia.com>
Date2017-05-02 17:30 +0200
SubjectRe: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout
Message-ID<tCHUt-8wt-3@gated-at.bofh.it>
In reply to#1634441
On 02/05/17 15:05, Laxman Dewangan wrote:
> The PWM hardware IP is taped-out with different maximum frequency
> on different SoCs.
> 
> From HW team:
> 	Before Tegra186, it is 38.4MHz.
> 	In Tegra186, it is 102MHz.
> 
> Add support to limit the clock source frequency to the maximum IP
> supported frequency. Provide these values via SoC chipdata.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> 
> ---
> Changes from V1:
> - Set the 48MHz maximum frequency for Tegra210 and earlier.

I think that your changelog needs to be updated, because it still says
38.4MHz and not 48MHz.

Cheers
Jon

-- 
nvpublic

[toc] | [prev] | [next] | [standalone]


#1634550

FromLaxman Dewangan <ldewangan@nvidia.com>
Date2017-05-02 19:50 +0200
Message-ID<tCK5X-1ke-1@gated-at.bofh.it>
In reply to#1634482
On Tuesday 02 May 2017 08:53 PM, Jon Hunter wrote:
> On 02/05/17 15:05, Laxman Dewangan wrote:
>> The PWM hardware IP is taped-out with different maximum frequency
>> on different SoCs.
>>
>>  From HW team:
>> 	Before Tegra186, it is 38.4MHz.
>> 	In Tegra186, it is 102MHz.
>>
>> Add support to limit the clock source frequency to the maximum IP
>> supported frequency. Provide these values via SoC chipdata.
>>
>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>>
>> ---
>> Changes from V1:
>> - Set the 48MHz maximum frequency for Tegra210 and earlier.
> I think that your changelog needs to be updated, because it still says
> 38.4MHz and not 48MHz.
>

Oops, thanks for pointing.

Thierry,
Do I need to recycle the patch or can be corrected when applying?
If there is any further review comment in code then I will recycle and 
correct it.

[toc] | [prev] | [next] | [standalone]


#1634603 — Re: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout

FromJon Hunter <jonathanh@nvidia.com>
Date2017-05-02 22:20 +0200
SubjectRe: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout
Message-ID<tCMr7-30x-1@gated-at.bofh.it>
In reply to#1634550
On 02/05/17 18:43, Laxman Dewangan wrote:
> 
> On Tuesday 02 May 2017 08:53 PM, Jon Hunter wrote:
>> On 02/05/17 15:05, Laxman Dewangan wrote:
>>> The PWM hardware IP is taped-out with different maximum frequency
>>> on different SoCs.
>>>
>>>  From HW team:
>>>     Before Tegra186, it is 38.4MHz.
>>>     In Tegra186, it is 102MHz.
>>>
>>> Add support to limit the clock source frequency to the maximum IP
>>> supported frequency. Provide these values via SoC chipdata.
>>>
>>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>>>
>>> ---
>>> Changes from V1:
>>> - Set the 48MHz maximum frequency for Tegra210 and earlier.
>> I think that your changelog needs to be updated, because it still says
>> 38.4MHz and not 48MHz.
>>
> 
> Oops, thanks for pointing.
> 
> Thierry,
> Do I need to recycle the patch or can be corrected when applying?
> If there is any further review comment in code then I will recycle and
> correct it.

Feel free to add my ...

Acked-by: Jon Hunter <jonathanh@nvidia.com>

Cheers
Jon

-- 
nvpublic

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web