From: Tony Lindgren <tony@atomide.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP3: hsmmc: fix MMC 2 setup for AM35x
Date: Thu, 8 Dec 2011 16:31:42 -0800 [thread overview]
Message-ID: <20111209003142.GG31337@atomide.com> (raw)
In-Reply-To: <4EE10F20.5080806@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [111208 10:53]:
> ping
>
> Tony,
> I'd like this to go into 3.3, can it?
>
> On 11/29/11 11:37, Igor Grinberg wrote:
> > AM35x MMC 2 controller has internal clock loopback setting which cannot
> > be utilized without this patch and thus SDIO devices connected to this
> > controller and depend on this setting will fail to initialize.
Yes seems OK for now so applying into omap driver branch.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP3: hsmmc: fix MMC 2 setup for AM35x
Date: Thu, 8 Dec 2011 16:31:42 -0800 [thread overview]
Message-ID: <20111209003142.GG31337@atomide.com> (raw)
In-Reply-To: <4EE10F20.5080806@compulab.co.il>
* Igor Grinberg <grinberg@compulab.co.il> [111208 10:53]:
> ping
>
> Tony,
> I'd like this to go into 3.3, can it?
>
> On 11/29/11 11:37, Igor Grinberg wrote:
> > AM35x MMC 2 controller has internal clock loopback setting which cannot
> > be utilized without this patch and thus SDIO devices connected to this
> > controller and depend on this setting will fail to initialize.
Yes seems OK for now so applying into omap driver branch.
Regards,
Tony
next prev parent reply other threads:[~2011-12-09 0:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 9:37 [PATCH] ARM: OMAP3: hsmmc: fix MMC 2 setup for AM35x Igor Grinberg
2011-11-29 9:37 ` Igor Grinberg
2011-12-08 19:25 ` Igor Grinberg
2011-12-08 19:25 ` Igor Grinberg
2011-12-09 0:31 ` Tony Lindgren [this message]
2011-12-09 0:31 ` Tony Lindgren
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=20111209003142.GG31337@atomide.com \
--to=tony@atomide.com \
--cc=grinberg@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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.