From: Marek Vasut <marex@denx.de>
To: Huang Shijie <b32955@freescale.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
artem.bityutskiy@linux.intel.com, shawn.guo@linaro.org,
Fabio Estevam <festevam@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] nand: gpmi-nand: Fix clock registration
Date: Mon, 8 Oct 2012 05:37:04 +0200 [thread overview]
Message-ID: <201210080537.04912.marex@denx.de> (raw)
In-Reply-To: <507249B1.7040308@freescale.com>
Dear Huang Shijie,
> 于 2012年10月08日 11:15, Marek Vasut 写道:
> > Dear Huang Shijie,
> >
> >> 于 2012年09月24日 02:31, Fabio Estevam 写道:
> >>> From: Fabio Estevam <fabio.estevam@freescale.com>
> >>>
> >>> On a mx28 board the following error happens since commit 638064e56c
> >>> (mtd: gpmi: change the code for clocks):
> >>>
> >>> gpmi-nand: probe of 8000c000.gpmi-nand failed with error -12
> >>>
> >>> Acquire the clock using "NULL" as it was done previously, so that the
> >>> driver can register on mx23/mx28 as well.
> >>>
> >>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> >>> ---
> >>>
> >>> drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 2 +-
> >>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> >>> b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c index c46be6c..1f23cb4 100644
> >>> --- a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> >>> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> >>> @@ -492,7 +492,7 @@ static int __devinit gpmi_get_clks(struct
> >>> gpmi_nand_data *this)
> >>>
> >>> int i;
> >>>
> >>> /* The main clock is stored in the first. */
> >>>
> >>> - r->clock[0] = clk_get(this->dev, "gpmi_io");
> >>> + r->clock[0] = clk_get(this->dev, NULL);
> >>
> >> Please do not change this line.
> >>
> >> The gpmi_io is for mx6q.
> >> If you replace it with `NULL`. The mx6q can not find the proper clock.
> >
> > Suggestion is really welcome though, please :) This is a problem, GPMI
> > NAND is broken on anything != mx6q. Huang, can you please also test the
> > changes you do to GPMI NAND on mx28/mx23 so we can avoid this breakage
> > in the future?
>
> yes. I tested in the mx23/mx28. It's ok, do not worry.
I won't be posting here that it's broken in the first place if it was ok ;-)
Give it one more go with latest -next ...
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-10-08 3:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 18:31 [PATCH] nand: gpmi-nand: Fix clock registration Fabio Estevam
2012-10-08 2:45 ` Huang Shijie
2012-10-08 3:15 ` Marek Vasut
2012-10-08 3:34 ` Huang Shijie
2012-10-08 3:37 ` Marek Vasut [this message]
2012-10-08 3:22 ` Fabio Estevam
2012-10-08 3:32 ` Huang Shijie
2012-10-08 3:31 ` Fabio Estevam
2012-10-08 3:46 ` Fabio Estevam
2012-10-08 3:52 ` Marek Vasut
2012-10-08 4:53 ` Huang Shijie
2012-10-10 2:44 ` Huang Shijie
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=201210080537.04912.marex@denx.de \
--to=marex@denx.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=b32955@freescale.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shawn.guo@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.