From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>, Chris Ball <chris@printf.net>
Cc: Balaji T K <balajitk@ti.com>, <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 1/2] mmc: omap_hsmmc: Add support for quirky omap3 hsmmc controller
Date: Fri, 28 Feb 2014 09:09:26 -0600 [thread overview]
Message-ID: <5310A6A6.6030803@ti.com> (raw)
In-Reply-To: <20140214163102.GA21592@atomide.com>
On 02/14/2014 10:31 AM, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [140213 21:48]:
>> When device is booted using devicetree, platforms impacted by Erratum
>> 2.1.1.128 is not detected easily in the mmc driver. This erratum
>> indicates that the module cannot do multi-block transfers. Platforms
>> such as LDP which use OMAP3 ES revision prior to ES3.0 are impacted by
>> this.
>>
>> Provide a new compatible property "ti,omap3-pre-es3-hsmmc" to allow
>> driver to determine if driver needs to implement quirks associated
>> with the specific module version (primarily because the IP revision
>> information is not sufficient for the same).
>>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>
> Looks good to me, would be good to get this into the -rc cycle
> as LDP is one of the automated boot testing boards for us.
>
> If you guys want me to pick up both of the patches let me know,
> otherwise feel free to add my ack.
>
Chris,
would you be picking up the series that fixes LDP dt boot behavior or
should Tony pick it up?
https://patchwork.kernel.org/patch/3650061/
https://patchwork.kernel.org/patch/3650031/
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>, Chris Ball <chris@printf.net>
Cc: devicetree@vger.kernel.org, Balaji T K <balajitk@ti.com>,
linux-doc@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2 1/2] mmc: omap_hsmmc: Add support for quirky omap3 hsmmc controller
Date: Fri, 28 Feb 2014 09:09:26 -0600 [thread overview]
Message-ID: <5310A6A6.6030803@ti.com> (raw)
In-Reply-To: <20140214163102.GA21592@atomide.com>
On 02/14/2014 10:31 AM, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [140213 21:48]:
>> When device is booted using devicetree, platforms impacted by Erratum
>> 2.1.1.128 is not detected easily in the mmc driver. This erratum
>> indicates that the module cannot do multi-block transfers. Platforms
>> such as LDP which use OMAP3 ES revision prior to ES3.0 are impacted by
>> this.
>>
>> Provide a new compatible property "ti,omap3-pre-es3-hsmmc" to allow
>> driver to determine if driver needs to implement quirks associated
>> with the specific module version (primarily because the IP revision
>> information is not sufficient for the same).
>>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>
> Looks good to me, would be good to get this into the -rc cycle
> as LDP is one of the automated boot testing boards for us.
>
> If you guys want me to pick up both of the patches let me know,
> otherwise feel free to add my ack.
>
Chris,
would you be picking up the series that fixes LDP dt boot behavior or
should Tony pick it up?
https://patchwork.kernel.org/patch/3650061/
https://patchwork.kernel.org/patch/3650031/
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/2] mmc: omap_hsmmc: Add support for quirky omap3 hsmmc controller
Date: Fri, 28 Feb 2014 09:09:26 -0600 [thread overview]
Message-ID: <5310A6A6.6030803@ti.com> (raw)
In-Reply-To: <20140214163102.GA21592@atomide.com>
On 02/14/2014 10:31 AM, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [140213 21:48]:
>> When device is booted using devicetree, platforms impacted by Erratum
>> 2.1.1.128 is not detected easily in the mmc driver. This erratum
>> indicates that the module cannot do multi-block transfers. Platforms
>> such as LDP which use OMAP3 ES revision prior to ES3.0 are impacted by
>> this.
>>
>> Provide a new compatible property "ti,omap3-pre-es3-hsmmc" to allow
>> driver to determine if driver needs to implement quirks associated
>> with the specific module version (primarily because the IP revision
>> information is not sufficient for the same).
>>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>
> Looks good to me, would be good to get this into the -rc cycle
> as LDP is one of the automated boot testing boards for us.
>
> If you guys want me to pick up both of the patches let me know,
> otherwise feel free to add my ack.
>
Chris,
would you be picking up the series that fixes LDP dt boot behavior or
should Tony pick it up?
https://patchwork.kernel.org/patch/3650061/
https://patchwork.kernel.org/patch/3650031/
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-02-28 15:10 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 [this message]
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
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=5310A6A6.6030803@ti.com \
--to=nm@ti.com \
--cc=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=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.