linux-kernel - Re: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 2 May 2017 23:13:49 +0530
From:   Laxman Dewangan <ldewangan@...dia.com>
To:     Jon Hunter <jonathanh@...dia.com>, <thierry.reding@...il.com>
CC:     <linux-pwm@...r.kernel.org>, <linux-tegra@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] pwm: tegra: Set maximum pwm clock source per SoC tapeout


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@...dia.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.