linux-kernel - Re: [PATCH] clk: at91: allow 24 Mhz clock as input for PLL

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, 17 Sep 2019 05:59:18 +0000
From:   <Eugen.Hristev@...rochip.com>
To:     <sboyd@...nel.org>, <alexandre.belloni@...tlin.com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-clk@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <mturquette@...libre.com>
CC:     <Nicolas.Ferre@...rochip.com>
Subject: Re: [PATCH] clk: at91: allow 24 Mhz clock as input for PLL



On 16.09.2019 22:52, Stephen Boyd wrote:

> Quoting Eugen.Hristev@...rochip.com (2019-09-10 23:39:20)
>> From: Eugen Hristev <eugen.hristev@...rochip.com>
>>
>> The PLL input range needs to be able to allow 24 Mhz crystal as input
>> Update the range accordingly in plla characteristics struct
>>
>> Signed-off-by: Eugen Hristev <eugen.hristev@...rochip.com>
>> ---
> 
> Is there a Fixes: tag for this? Seems like it was always wrong?
> 

Hi Stephen,

At the initial design , the 12 Mhz was the only possibility for the 
boards themselves. But, with the commit who added this:

Fixes: c561e41ce4d2 ("clk: at91: add sama5d2 PMC driver")

Eugen