From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Date: Wed, 23 Apr 2014 00:22:54 +0000 Subject: Re: [PATCH 05/14] ARM: shmobile: koelsch-reference: Work around core clock issues Message-Id: <20140423002254.GD5738@verge.net.au> List-Id: References: <53cf0cf7ba2ef785b339826a0765bb6b1756adeb.1397774191.git.horms+renesas@verge.net.au> <5356D0B8.5010406@cogentembedded.com> In-Reply-To: <5356D0B8.5010406@cogentembedded.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-arm-kernel@lists.infradead.org On Wed, Apr 23, 2014 at 12:27:36AM +0400, Sergei Shtylyov wrote: > Hello. > > On 04/18/2014 02:44 AM, Simon Horman wrote: > > >From: Geert Uytterhoeven > > >Due to issues with runtime PM clock management, clocks not explicitly > >managed by their drivers may not be enabled at all, or be inadvertently > >disabled by the clk_disable_unused() late initcall. > > >Until this is fixed, add a temporary workaround, calling > >shmobile_clk_workaround() with enable = true. > > >For now this enables the clocks for: ether, i2c2, msiof0, qspi_mod, and > >thermal. More clocks can be added if needed. > > >Signed-off-by: Geert Uytterhoeven > >Signed-off-by: Simon Horman > > It is strange but this workaround doesn't seem to help me booting Koelsch > reference kernel with NFS root: it still crashes due to imprecise > external abort once the userland starts. Only the actual drivers/sh/ > fixing series by Ben/Geert helps with booting further. I therefore > would like to have it merged by Simon the sooner the better... For my reference, specifically which patches are you referring to?