From: Nishanth Menon <nm@ti.com>
To: a-bindra@ti.com
Cc: linux-mmc@vger.kernel.org, cjb@laptop.org,
linux-omap@vger.kernel.org, Balaji T K <balajitk@ti.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH v2] mmc: omap_hsmmc: use the generic config for omap2plus devices
Date: Wed, 10 Jul 2013 16:13:57 -0500 [thread overview]
Message-ID: <20130710211356.GA2587@snafu> (raw)
In-Reply-To: <1373472384-13067-1-git-send-email-a-bindra@ti.com>
On 21:36-20130710, a-bindra@ti.com wrote:
> From: Amarinder Bindra <a-bindra@ti.com>
>
> OMAP's hs_mmc driver is used for MMC controller operation on many
> omap2plus SoCs (OMAP2430, OMAP3, 4, 5 and AM335x).
>
> Considering that the device tree entries are already present for these,
> allow the driver to be built using the config ARCH_OMAP2PLUS rather
> than individually adding a config for each SoC to enable the
> support.
>
> Use COMPILE_TEST to enable the build for other platforms.
>
> Signed-off-by: Amarinder Bindra <a-bindra@ti.com>
> Cc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Nishanth Menon <nm@ti.com>
works for O5.
Acked-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-07-10 21:14 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
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 [this message]
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=20130710211356.GA2587@snafu \
--to=nm@ti.com \
--cc=a-bindra@ti.com \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=cjb@laptop.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-mmc@vger.kernel.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 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).