From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Angus Ainslie <angus@akkea.ca>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
David Woodhouse <dwmw2@infradead.org>,
Richard Weinberger <richard@nod.at>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Chen-Yu Tsai <wens@csie.org>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: CHIPPro NAND issue with 4.12 rc1
Date: Tue, 23 May 2017 21:52:39 +0200 [thread overview]
Message-ID: <20170523195239.6nsv4ydrt4u7q6ge@flea.home> (raw)
In-Reply-To: <63aca137397dc3700a34993205c8cfba@www.akkea.ca>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Mon, May 22, 2017 at 10:32:42AM -0600, Angus Ainslie wrote:
> 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.
Ok, good.
If you unrevert those patches, and add clk_ignore_unused to the kernel
command line, is it still broken?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-05-23 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 14:49 Angus Ainslie
2017-05-20 15:14 ` Boris Brezillon
2017-05-20 21:24 ` Angus Ainslie
2017-05-21 5:45 ` Boris Brezillon
2017-05-22 4:52 ` Angus Ainslie
2017-05-22 7:01 ` Maxime Ripard
2017-05-22 16:32 ` Angus Ainslie
2017-05-23 19:52 ` Maxime Ripard [this message]
2017-05-23 22:46 ` Angus Ainslie
2017-05-24 4:05 ` Angus Ainslie
2017-05-24 6:34 ` Maxime Ripard
2017-05-24 11:47 ` Angus Ainslie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170523195239.6nsv4ydrt4u7q6ge@flea.home \
--to=maxime.ripard@free-electrons.com \
--cc=angus@akkea.ca \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=wens@csie.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®