[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <63aca137397dc3700a34993205c8cfba@www.akkea.ca>
Date: Mon, 22 May 2017 10:32:42 -0600
From: Angus Ainslie <angus@...ea.ca>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>
Cc: Boris Brezillon <boris.brezillon@...e-electrons.com>,
David Woodhouse <dwmw2@...radead.org>,
Richard Weinberger <richard@....at>,
Brian Norris <computersforpeace@...il.com>,
Marek Vasut <marek.vasut@...il.com>,
Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>,
Chen-Yu Tsai <wens@...e.org>, linux-mtd@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: CHIPPro NAND issue with 4.12 rc1
Hi Maxime
On 2017-05-22 01:01, Maxime Ripard wrote:
>
> This just made me realise, this is also the time where the clocks are
> disabled, and we changed our clock implementation in 4.11.
>
> And using the 4.4 DT will keep the old driver...
>
> Did you test in 4.11? If it's also broken, could you try to revert
> 1f4ce3b6ca79 and 6b48644b1d29 (I'm not sure it's going to be a trivial
> revert, but in that order it should work).
>
Thanks reverting those two allow the kernel to boot and mount the NAND.
Powered by blists - more mailing lists