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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1501845448.17254.31.camel@nxp.com>
Date:   Fri, 4 Aug 2017 14:17:28 +0300
From:   Leonard Crestez <leonard.crestez@....com>
To:     Sébastien Szymanski 
        <sebastien.szymanski@...adeus.com>,
        Shawn Guo <shawnguo@...nel.org>,
        "Anson Huang" <anson.huang@....com>, Jacky Bai <ping.bai@....com>
CC:     <linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>,
        Viresh Kumar <viresh.kumar@...aro.org>,
        "Rafael J. Wysocki" <rjw@...ysocki.net>,
        "Julien Boibessot" <julien.boibessot@...adeus.com>,
        Fabio Estevam <fabio.estevam@....com>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/1] cpufreq: imx6q: imx6ull: use PLL1 for frequency
 higher than 528MHz

On Thu, 2017-08-03 at 09:32 +0200, Sébastien Szymanski wrote:
> On 08/03/2017 04:03 AM, Shawn Guo wrote:
> > On Fri, Jul 28, 2017 at 10:36:33AM +0200, Sébastien Szymanski wrote:
> > > Setting the frequency higher than 528Mhz actually sets the ARM
> > > clock to 528MHz. That's because PLL2 is used as the root clock when the
> > > frequency is higher than 396MHz.
> > > 
> > > cpupower frequency-set -f 792000
> > > 
> > > arm_clk_root on the CCM_CLKO2 signal is 528MHz instead of 792MHz.
> > > 
> > > [   61.606383] cpu cpu0: 396 MHz, 1025 mV --> 792 MHz, 1225 mV
> > > 
> > > pll2                         1  1  528000000 0 0
> > >    pll2_bypass               1  1  528000000 0 0
> > >       pll2_bus               3  3  528000000 0 0
> > > 	 ca7_secondary_sel   1  1  528000000 0 0
> > > 	    step             1  1  528000000 0 0
> > > 	       pll1_sw       1  1  528000000 0 0
> > > 		  arm        1  1  528000000 0 0
> > > 
> > > Fixes this by using the PLL1 as the root clock when the frequency is
> > > higher than 528MHz.
> > > 
> > > cpupower frequency-set -f 792000
> > > 
> > > arm_clk_root on the CCM_CLKO2 signal is now 792MHz as expected.
> > > 
> > > [   69.717987] cpu cpu0: 198 MHz, 950 mV --> 792 MHz, 1225 mV
> > > 
> > > pll1               1 1 792000000 0 0
> > >    pll1_bypass     1 1 792000000 0 0
> > >       pll1_sys     1 1 792000000 0 0
> > > 	 pll1_sw   1 1 792000000 0 0
> > > 	    arm    1 1 792000000 0 0
> > > 
> > > Signed-off-by: Sébastien Szymanski <sebastien.szymanski@...adeus.com>
> > 
> > Can you please specify on which SoCs you are seeing this problem?  And I
> > would like invite Anson and Leonard to review it.
> 
> My SoC is MCIMX6Y2CVM08AA which is a 792MHz i.MX6ULL. I forgot to
> mention that I added the following operating points in my device tree:
> 
> operating-points: 792000  1225000
> fsl,soc-operating-points: 792000  1175000

Yeah, I was wondering about that.

Adding support for higher imx6ul/ull frequencies "properly" requires adding the extra OPPs to .dtsi (they are different between 6ul and 6ull) and reading the speed grading from OCOTP to check if they are supported.

This patch can only work if you hack OPPs for a specific board.

Reading the speed grading is essential because otherwise you risk causing random crashes while running at frequencies not supported by the hardware.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ