From: Tony Lindgren <tony@atomide.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Grazvydas Ignotas <notasas@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] HSMMC: Make loopback clock configurable
Date: Fri, 14 Nov 2008 10:48:48 -0800 [thread overview]
Message-ID: <20081114184847.GL3106@atomide.com> (raw)
In-Reply-To: <5e088bd90811141034l4d5cc1ddl9e2852f69486216c@mail.gmail.com>
* Steve Sakoman <sakoman@gmail.com> [081114 10:34]:
> On Fri, Nov 14, 2008 at 2:49 AM, Grazvydas Ignotas <notasas@gmail.com> wrote:
> > On Fri, Nov 14, 2008 at 8:41 AM, Steve Sakoman <sakoman@gmail.com> wrote:
> >> On Thu, Nov 13, 2008 at 3:06 PM, Tony Lindgren <tony@atomide.com> wrote:
> >>> * Grazvydas Ignotas <notasas@gmail.com> [081113 13:40]:
> >>>> Some boards use input clock from external pin for MMC/SDIO
> >>>> modules in OMAP chips. Make that option selectable instead of
> >>>> forcing loop back clock on everyone.
> >>>
> >>> Thanks, pushing both today.
> >>
> >> Hmm . . . not sure if it is related to this patch, but I now get an
> >> oops on Overo.
> >
> > Oops.. Haven't thought to try it without gpio_cd set up, in which case c->mmc
> > is not set initialized.. Please try the following patch:
>
> I did, and I am happy to report that it fixed the oops on mmc2 and my
> wi2wi driver is happily working again.
Grazvydas, can you please reply with your S-O-B so I can push your fix?
Thanks,
Tony
>
> Thanks!
>
> Steve
>
> > diff --git a/arch/arm/mach-omap2/mmc-twl4030.c b/arch/arm/mach-omap2/mmc-twl4030.c
> > index 0ea6ba6..626d668 100644
> > --- a/arch/arm/mach-omap2/mmc-twl4030.c
> > +++ b/arch/arm/mach-omap2/mmc-twl4030.c
> > @@ -239,6 +239,7 @@ static int twl_mmc1_set_power(struct device *dev, int slot, int power_on,
> > u32 reg;
> > int ret = 0;
> > struct twl_mmc_controller *c = &hsmmc[0];
> > + struct omap_mmc_platform_data *mmc = dev->platform_data;
> >
> > if (power_on) {
> > if (cpu_is_omap2430()) {
> > @@ -250,7 +251,7 @@ static int twl_mmc1_set_power(struct device *dev, int slot, int power_on,
> > omap_ctrl_writel(reg, OMAP243X_CONTROL_DEVCONF1);
> > }
> >
> > - if (c->mmc->slots[0].internal_clock) {
> > + if (mmc->slots[0].internal_clock) {
> > reg = omap_ctrl_readl(OMAP2_CONTROL_DEVCONF0);
> > reg |= OMAP2_MMCSDIO1ADPCLKISEL;
> > omap_ctrl_writel(reg, OMAP2_CONTROL_DEVCONF0);
> > @@ -293,11 +294,11 @@ static int twl_mmc1_set_power(struct device *dev, int slot, int power_on,
> > static int twl_mmc2_set_power(struct device *dev, int slot, int power_on, int vdd)
> > {
> > int ret;
> > -
> > struct twl_mmc_controller *c = &hsmmc[1];
> > + struct omap_mmc_platform_data *mmc = dev->platform_data;
> >
> > if (power_on) {
> > - if (c->mmc->slots[0].internal_clock) {
> > + if (mmc->slots[0].internal_clock) {
> > u32 reg;
> >
> > reg = omap_ctrl_readl(control_devconf1_offset);
> >
next prev parent reply other threads:[~2008-11-14 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 21:40 [PATCH 1/2] HSMMC: Make loopback clock configurable Grazvydas Ignotas
2008-11-13 21:40 ` [PATCH 2/2] HSMMC: Enable external input clock for 2430 SDP MMC1 Grazvydas Ignotas
2008-11-13 23:06 ` [PATCH 1/2] HSMMC: Make loopback clock configurable Tony Lindgren
2008-11-14 6:41 ` Steve Sakoman
2008-11-14 10:49 ` Grazvydas Ignotas
2008-11-14 18:34 ` Steve Sakoman
2008-11-14 18:48 ` Tony Lindgren [this message]
2008-11-14 18:54 ` Koen Kooi
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=20081114184847.GL3106@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=sakoman@gmail.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