From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Nishanth Menon <nm@TI.COM>
Cc: Felipe Balbi <balbi@TI.COM>, Balaji T K <balajitk@TI.COM>,
a-bindra@TI.COM, linux-mmc@vger.kernel.org, cjb@laptop.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] mmc: omap_hsmmc: use for OMAP5 as well
Date: Mon, 8 Jul 2013 17:27:50 -0300 [thread overview]
Message-ID: <20130708202749.GA2596@localhost> (raw)
In-Reply-To: <20130708195828.GA28218@kahuna>
On Mon, Jul 08, 2013 at 02:58:28PM -0500, Nishanth Menon wrote:
> On 10:46-20130708, Felipe Balbi wrote:
> > On Sun, Jul 07, 2013 at 05:13:10PM -0300, Ezequiel Garcia wrote:
> > > Hi guys,
> > >
> > > On Fri, Jun 28, 2013 at 09:27:20PM +0530, Balaji T K wrote:
> > > > On Friday 28 June 2013 06:04 PM, a-bindra@ti.com wrote:
> > > > > From: Amarinder Bindra <a-bindra@ti.com>
> > > > >
> > > > > OMAP's hs_mmc driver is also used for OMAP5 MMC controller operation.
> > > > > Considering that the device tree entries are already there for this,
> > > > > allow the driver to be built when only OMAP5 is enabled.
> > > > > This allows MMC root filesystems to be available in "OMAP5 only"
> > > > > configurations.
> > > > >
> > > > > Signed-off-by: Amarinder Bindra <a-bindra@ti.com>
> > > > > Acked-by: Felipe Balbi <balbi@ti.com>
> > > > > Acked-by: Nishanth Menon <nm@ti.com>
> > > >
> > > > Looks good to me,
> > > > Acked-by: Balaji T K <balajitk@ti.com>
> > > >
> > >
> > > I came across this same issue while trying MMC patches on AM3xx,
> > > which is nor OMAP3 neither OMAP4.
> > >
> > > Now, looking at the driver I don't see any OMAP-specific bits
> > > (welcome to the multiplatform world ;-) so I think we can just
> > > remove the 'depends' line. Something like this:
> >
> > frankly speaking, this driver should be deleted and all users should be
> > moved to sdhci. OMAP's HSMMC controller is compatible with SDHCI except
> > for a couple quirks which can be easily worked around.
@Felipe:
Do you mind giving me some hints about this quirks? I'm not too familiar
with these drivers.
> Do we take that as a NAK to this specific patch?
>
> I am not complaining about the future migration to a solution that is
> much more generic and scalable, but having fixes for current problems
> should'nt be ignored IMHO.
>
Of course.
> How about a depends on CONFIG_ARCH_OMAP2PLUS instead? will that solve
> our pains with all OMAP2+ usin this?
Yes, I think that using ARCH_OMAP2PLUS should do. FWIW, until we have
sdhci ready to replace omap_hsmmc, we have no choice but to apply such
a patch.
@Nishant, Balaji: Can you take care of resending this?
Thanks!
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-07-08 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 12:34 [PATCH] mmc: omap_hsmmc: use for OMAP5 as well a-bindra
2013-06-28 15:57 ` Balaji T K
2013-07-07 20:13 ` Ezequiel Garcia
2013-07-08 7:46 ` Felipe Balbi
2013-07-08 19:58 ` Nishanth Menon
2013-07-08 20:27 ` Ezequiel Garcia [this message]
2013-07-09 6:55 ` Felipe Balbi
2013-07-09 6:52 ` Felipe Balbi
2013-07-10 16:06 ` [PATCH v2] mmc: omap_hsmmc: use the generic config for omap2plus devices a-bindra
2013-07-10 21:13 ` Nishanth Menon
2013-07-10 22:42 ` Ezequiel Garcia
2013-07-11 13:09 ` Felipe Balbi
2013-08-16 16:35 ` Balaji T K
2013-08-25 19:51 ` Chris Ball
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=20130708202749.GA2596@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=a-bindra@TI.COM \
--cc=balajitk@TI.COM \
--cc=balbi@TI.COM \
--cc=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@TI.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;
as well as URLs for NNTP newsgroup(s).