From: balajitk@ti.com (Balaji T K)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] AM33xx: MMC resources from DT without HWMOD data
Date: Fri, 28 Jun 2013 21:18:59 +0530 [thread overview]
Message-ID: <51CDB06B.9010604@ti.com> (raw)
In-Reply-To: <083BC63EECB6FD41B8E81CF7FD87CC0F2E4F0F95@DLEE08.ent.ti.com>
On Thursday 27 June 2013 11:38 PM, Fernandes, Joel wrote:
> Hi Balaji,
>
<snip>
>>> 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
>
> Actually this is an independent regression and is currently worked on by Lars-Peter Clausen [1].
>
> Currently not having the MMC DTS merged is also a regression,
No, Right now mmc support is not added to am335x, so it is not really a regression
> so I suggest lets take it one
> step at a time and get the DTS merged in first. Also there will be overhead of reposting this
> DTS patch later again which will not change. What do you say?
>
If it gets enabled via dts, without slave sg limit support,
file read/write will fail, possibly corrupting file system.
> Thanks,
>
> -Joel
>
> [1] https://patchwork.kernel.org/patch/2228041/
>
next prev parent reply other threads:[~2013-06-28 15:48 UTC|newest]
Thread overview: 9+ 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
2013-06-26 3:28 ` Joel A Fernandes
2013-06-27 12:03 ` Benoit Cousson
2013-06-27 14:26 ` Joel A Fernandes
2013-06-27 16:26 ` Balaji T K
2013-06-27 18:08 ` Fernandes, Joel
2013-06-28 15:48 ` Balaji T K [this message]
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=51CDB06B.9010604@ti.com \
--to=balajitk@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).