public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balaji T K <balajitk@ti.com>
To: Benoit Cousson <b-cousson@ti.com>, <joelf@ti.com>
Cc: <lars@metafoo.de>, Tony Lindgren <tony@atomide.com>,
	Sekhar Nori <nsekhar@ti.com>, Matt Porter <matt@ohporter.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	Vinod Koul <vinod.koul@intel.com>,
	Mark Brown <broonie@linaro.org>,
	Russell King <linux@arm.linux.org.uk>,
	Rob Landley <rob@landley.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jason Kridner <jkridner@beagleboard.org>,
	Koen Kooi <koen@beagleboard.org>, Chris Ball <cjb@laptop.org>,
	Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>,
	Linux OMAP List <linux-omap@vger.kernel.org>,
	Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
	Linux DaVinci Kernel List 
	<davinci-linux-open-source@linux.davincidsp.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux MMC List <linux-mmc@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 0/5] AM33xx: MMC resources from DT without HWMOD data
Date: Thu, 27 Jun 2013 21:56:50 +0530	[thread overview]
Message-ID: <51CC67CA.2070805@ti.com> (raw)
In-Reply-To: <CAD=GYpa9LQ1fV6=O9B65sJURVAigsgXCPLWav8cHXTuGQXPc9A@mail.gmail.com>

On Thursday 27 June 2013 07:56 PM, Joel A Fernandes wrote:
> Hi Benoit,
>
> On Thu, Jun 27, 2013 at 7:03 AM, Benoit Cousson <b-cousson@ti.com> wrote:
>> Hi Joel,
>>
>> On 06/26/2013 05:28 AM, Joel A Fernandes wrote:
>>> On Tue, Jun 25, 2013 at 8:23 PM, Joel A Fernandes <joelagnel@ti.com> wrote:
>>>> From: Joel A Fernandes <agnel.joel@gmail.com>
>>>>
>>>> This series is fixes to get MMC working on AM33XX without HWMOD data.
>>>> On removal of HWMOD data, interrupt and register properties need to be provided
>>>> for the driver to function correctly.
>>>
>>> Please don't pull patches authored by me in this series. I have posted
>>> them with my wrong email address by mistake. I will correct my email
>>> during the next repost, after a round of review. Matt's patches in the
>>> series are still good though.
>>
>> In that case, please repost these in two series to avoid pulling the DTS
>> files in the MMC tree.
>
> The series has been replaced with the single patch:
> "[PATCH v2] ARM: dts: add AM33XX MMC support"
> http://marc.info/?l=linux-omap&m=137230403815943&w=2
>
> Some patches were squashed and others dropped in the series resulting
> in the single
> patch above. This patch should be good to apply
Hi Joel,

Before pushing mmc dts support for am335x, Can you please let me
know if below 2 patches [1] are merged/accepted,
IIRC these patches are needed for MMC to work properly.

I suggest to hold the dts patch until slave_sg_limit gets merged
otherwise it will cause regression in am335x mmc.

[PATCH v4 1/3] dmaengine: add dma_get_slave_sg_limits()
[PATCH v4 2/3] dma: edma: add device_slave_sg_limits() support

[1]
https://groups.google.com/forum/#!topic/linux.kernel/khTTcPtQpag

>
> Thanks,
>
> -Joel
>

  parent reply	other threads:[~2013-06-27 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26  1:23 [PATCH 0/5] AM33xx: MMC resources from DT without HWMOD data Joel A Fernandes
     [not found] ` <CAD=GYpbdVVrh-tiqOcbHi3mkWRJUBdx0EsEZEFVVbgFgcCWgsw@mail.gmail.com>
2013-06-27 12:03   ` Benoit Cousson
     [not found]     ` <CAD=GYpa9LQ1fV6=O9B65sJURVAigsgXCPLWav8cHXTuGQXPc9A@mail.gmail.com>
2013-06-27 16:26       ` Balaji T K [this message]
2013-06-27 18:08         ` Fernandes, Joel
2013-06-28 15:48           ` Balaji T K
2013-06-28 16:56             ` Fernandes, Joel
2013-06-27 18:10         ` Fernandes, Joel

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=51CC67CA.2070805@ti.com \
    --to=balajitk@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=b-cousson@ti.com \
    --cc=broonie@linaro.org \
    --cc=cjb@laptop.org \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jkridner@beagleboard.org \
    --cc=joelf@ti.com \
    --cc=koen@beagleboard.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=matt@ohporter.com \
    --cc=nsekhar@ti.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=tony@atomide.com \
    --cc=vinod.koul@intel.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