From: Sascha Hauer <s.hauer@pengutronix.de>
To: Dmitry Lavnikevich <d.lavnikevich@sam-solutions.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] mtd: nand-mxs: Gate ENFC_CLK_ROOT clock off before changing nand clock rate
Date: Wed, 19 Nov 2014 07:44:15 +0100 [thread overview]
Message-ID: <20141119064415.GJ14482@pengutronix.de> (raw)
In-Reply-To: <1416175114-3132-1-git-send-email-d.lavnikevich@sam-solutions.com>
On Mon, Nov 17, 2014 at 12:58:34AM +0300, Dmitry Lavnikevich wrote:
> This fixes NAND initialization issue which appears occasionally on
> some i.MX6 SoCs (particulary was observed on phyCARD-i.MX6 with
> i.MX6Solo).
>
> Signed-off-by: Dmitry Lavnikevich <d.lavnikevich@sam-solutions.com>
I had to revert this one. It breaks compilation on i.MX28. Looking
closer at it reveals this is the wrong approach.
> if (mxs_nand_is_imx6(nand_info)) {
> + val = readl(MXC_CCM_CCGR2);
> + val &= ~MXC_CCM_CCGR2_IOMUX_IPT_CLK_IO_MASK;
> + writel(val, MXC_CCM_CCGR2);
> +
> clk_set_rate(nand_info->clk, 96000000);
> +
> + val = readl(MXC_CCM_CCGR2);
> + val |= MXC_CCM_CCGR2_IOMUX_IPT_CLK_IO_MASK;
> + writel(val, MXC_CCM_CCGR2);
> +
> clk_enable(nand_info->clk);
First of all please look at the kernel driver. It uses a clock of 22MHz
normally and 100 or 80MHz for EDO mode, which seems to require setup of
other registers. So it might be that there's something else that makes
trouble here.
The clk API is for abstracting the clock providers from its consumers.
It's unnecessary to directly fiddle with the clock registers in the nand
driver. Instead of passing the enfc_podf to the nand controller
arch/arm/mach-imx/clk-imx6.c should be changed to pass the gate to the
controller and here. In the final enabling of all the gates in
clk-imx6.c clear MXC_CCM_CCGR2[14..15] and enable the clock here after
setting the rate.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-11-19 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 21:58 Dmitry Lavnikevich
2014-11-17 7:39 ` Sascha Hauer
2014-11-19 6:44 ` Sascha Hauer [this message]
2014-11-19 14:34 ` Dmitry Lavnikevich
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=20141119064415.GJ14482@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=d.lavnikevich@sam-solutions.com \
/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