From: Marek Vasut <marex@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
Huang Shijie <b32955@freescale.com>,
shawn.guo@linaro.org, linux-mtd@lists.infradead.org,
artem.bityutskiy@linux.intel.com
Subject: Re: [PATCH] nand: gpmi-nand: Fix clock registration
Date: Mon, 8 Oct 2012 05:52:20 +0200 [thread overview]
Message-ID: <201210080552.20661.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5CYgDi3Rj7gKJAr-nMrUSec4YAxLCkPPf-amA6nXP7_EA@mail.gmail.com>
Dear Fabio Estevam,
> On Mon, Oct 8, 2012 at 12:31 AM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Mon, Oct 8, 2012 at 12:32 AM, Huang Shijie <b32955@freescale.com> wrote:
> >> This patch is really not needed.
> >>
> >> The clk_get() can get the right clock in the mx23/mx28. I tested them.
> >
> > Please test it on linux-next.
> >
> > gpmi nand can not event be probed.
>
> What about this?
I don't like this one ... such condition shouldn't be in the driver.
> --- a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
> @@ -495,7 +495,11 @@ 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");
> + if (GPMI_IS_MX6Q(this))
> + r->clock[0] = clk_get(this->dev, "gpmi_io");
> + else
> + r->clock[0] = clk_get(this->dev, NULL);
> +
> if (IS_ERR(r->clock[0]))
> goto err_clock;
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-10-08 3:52 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
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 [this message]
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=201210080552.20661.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox