From: Balaji T K <balajitk@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, Chris Ball <chris@printf.net>,
<linux-mmc@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH V2 2/2] ARM: dts: omap3-ldp: fix mmc configuration
Date: Thu, 20 Feb 2014 18:51:45 +0530 [thread overview]
Message-ID: <53060169.2050207@ti.com> (raw)
In-Reply-To: <1392356749-32091-3-git-send-email-nm@ti.com>
On Friday 14 February 2014 11:15 AM, Nishanth Menon wrote:
> MMC1 is the only MMC interface available on the platform. Further,
> since the platform is based on older revision of SoC which is not
> capable of doing multi-block reads, mark it with compatibility for the
> same and add pinmux to ensure that all relevant pins are configured
> for non-MMC boot mode.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
looks good to me
Acked-by: Balaji T K <balajitk@ti.com>
WARNING: multiple messages have this Message-ID (diff)
From: Balaji T K <balajitk@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
Tony Lindgren <tony@atomide.com>,
linux-mmc@vger.kernel.org, Chris Ball <chris@printf.net>,
Felipe Balbi <balbi@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 2/2] ARM: dts: omap3-ldp: fix mmc configuration
Date: Thu, 20 Feb 2014 18:51:45 +0530 [thread overview]
Message-ID: <53060169.2050207@ti.com> (raw)
In-Reply-To: <1392356749-32091-3-git-send-email-nm@ti.com>
On Friday 14 February 2014 11:15 AM, Nishanth Menon wrote:
> MMC1 is the only MMC interface available on the platform. Further,
> since the platform is based on older revision of SoC which is not
> capable of doing multi-block reads, mark it with compatibility for the
> same and add pinmux to ensure that all relevant pins are configured
> for non-MMC boot mode.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
looks good to me
Acked-by: Balaji T K <balajitk@ti.com>
WARNING: multiple messages have this Message-ID (diff)
From: balajitk@ti.com (Balaji T K)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/2] ARM: dts: omap3-ldp: fix mmc configuration
Date: Thu, 20 Feb 2014 18:51:45 +0530 [thread overview]
Message-ID: <53060169.2050207@ti.com> (raw)
In-Reply-To: <1392356749-32091-3-git-send-email-nm@ti.com>
On Friday 14 February 2014 11:15 AM, Nishanth Menon wrote:
> MMC1 is the only MMC interface available on the platform. Further,
> since the platform is based on older revision of SoC which is not
> capable of doing multi-block reads, mark it with compatibility for the
> same and add pinmux to ensure that all relevant pins are configured
> for non-MMC boot mode.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
looks good to me
Acked-by: Balaji T K <balajitk@ti.com>
next prev parent reply other threads:[~2014-02-20 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 5:45 [PATCH V2 0/2] mmc: omap_hsmmc: fix for pre es3.0 OMAP3 Nishanth Menon
2014-02-14 5:45 ` Nishanth Menon
2014-02-14 5:45 ` Nishanth Menon
2014-02-14 5:45 ` [PATCH V2 1/2] mmc: omap_hsmmc: Add support for quirky omap3 hsmmc controller Nishanth Menon
2014-02-14 5:45 ` Nishanth Menon
2014-02-14 5:45 ` Nishanth Menon
2014-02-14 16:31 ` Tony Lindgren
2014-02-14 16:31 ` Tony Lindgren
2014-02-28 15:09 ` Nishanth Menon
2014-02-28 15:09 ` Nishanth Menon
2014-02-28 15:09 ` Nishanth Menon
2014-02-18 14:36 ` Balaji T K
2014-02-18 14:36 ` Balaji T K
2014-02-18 14:36 ` Balaji T K
2014-02-14 5:45 ` [PATCH V2 2/2] ARM: dts: omap3-ldp: fix mmc configuration Nishanth Menon
2014-02-14 5:45 ` Nishanth Menon
2014-02-14 5:45 ` Nishanth Menon
2014-02-20 13:21 ` Balaji T K [this message]
2014-02-20 13:21 ` Balaji T K
2014-02-20 13:21 ` Balaji T K
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=53060169.2050207@ti.com \
--to=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.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 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.