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] [day] [month] [year] [list]
Message-ID: <1472642915.31008.32.camel@toradex.com>
Date:   Wed, 31 Aug 2016 11:28:36 +0000
From:   Marcel Ziswiler <marcel.ziswiler@...adex.com>
To:     "mirza.krak@...il.com" <mirza.krak@...il.com>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "jonathanh@...dia.com" <jonathanh@...dia.com>,
        "mturquette@...libre.com" <mturquette@...libre.com>,
        "pgaikwad@...dia.com" <pgaikwad@...dia.com>,
        "linux@...linux.org.uk" <linux@...linux.org.uk>,
        "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
        "gnurou@...il.com" <gnurou@...il.com>,
        "mchourasia@...dia.com" <mchourasia@...dia.com>,
        "thierry.reding@...il.com" <thierry.reding@...il.com>,
        "mark.rutland@....com" <mark.rutland@....com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "pdeschrijver@...dia.com" <pdeschrijver@...dia.com>,
        "sboyd@...eaurora.org" <sboyd@...eaurora.org>,
        "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
        "swarren@...dotorg.org" <swarren@...dotorg.org>,
        "linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>
Subject: Re: [Fwd: Re: [PATCH v2 1/6] clk: tegra: add TEGRA20_CLK_NOR to init
 table]

On Wed, 2016-08-31 at 11:47 +0200, Mirza Krak wrote:
> I'm just curious where that 92 MHz came from. According to the
> > Tegra 2
> > Interface Design Guide up to 133 MHz should actually be possible.
> The maximum rates for both T20 and T30 are values that are set as
> maximum in the downstream L4T kernel.
> 
> In tegra2_clocks.c:
> PERIPH_CLK("nor", "tegra-nor", NULL, 42, 0x1d0, 0x31E, 92000000,
> mux_pllp_pllc_pllm_clkm, MUX | DIV_U71), /* requires min voltage */
> 
> And in tegra3_clocks.c
> PERIPH_CLK("nor", "tegra-nor", NULL, 42, 0x1d0, 127000000,
> mux_pllp_pllc_pllm_clkm, MUX | DIV_U71), /* requires min voltage */
> 
> I looked up the commit in the downstream kernel that added the "nor"
> clock, it does not mention reason behind the maximal rates. Author
> was
> Manoj Chourasia, added him to CC.

Let's see whether we do get any feedback from him.

Nonetheless it may be good to add this information to the commit
message so should somebody ever feel the same curiosity like I did he
would at least know where it initially came from.

> I actually do not have the Tegra2 Interface Design Guide, do not know
> if I can get access to it.

I guess that one is only accessible under NDA. We could of course try
to get one in place for you but I can't promise you anything.

> Best Regards
> Mirza

Thanks, Mirza

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ