From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: EDMA: Fix clearing of unused list for DT DMA resources
Date: Tue, 30 Jul 2013 10:22:24 +0530 [thread overview]
Message-ID: <51F74688.3090702@ti.com> (raw)
In-Reply-To: <51F738BF.7070808@ti.com>
On Tuesday 30 July 2013 09:23 AM, Joel Fernandes wrote:
> On 07/29/2013 02:04 AM, Sekhar Nori wrote:
>> On Sunday 28 July 2013 05:02 AM, Joel Fernandes wrote:
>>> Hi Tony or Sekhar,
>>>
>>> If this patch looks ok, could you pick it up for -rc cycle?
>>>
>>> It fixes DMA breakages after the merge window for devices for which DMA
>>> resources are being populated in device tree instead pdev.
>>
>> But which DT-enabled platform in kernel is using EDMA? A grep for edma
>> over arch/arm/boot/dts/* brings up nothing.
>> Does this really have to go into the -rc cycle or can it wait till
>> v3.12?
>
>
> But unused channel list is also populated for private EDMA callers like
> davinci-pcm no? IIRC, HWMOD data is also removed for McASP so EDMA for
> those may break.
Yes, but which DT-enabled platform has davinci-pcm working today?
AFAICS, this bug affects DT-enabled platforms only.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-07-30 4:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 17:59 [PATCH v2] ARM: EDMA: Fix clearing of unused list for DT DMA resources Joel Fernandes
2013-07-27 23:32 ` Joel Fernandes
2013-07-29 7:04 ` Sekhar Nori
2013-07-30 3:53 ` Joel Fernandes
2013-07-30 4:52 ` Sekhar Nori [this message]
2013-07-30 5:05 ` Joel Fernandes
2013-07-29 7:01 ` Sekhar Nori
2013-07-30 3:47 ` Joel Fernandes
2013-07-30 16:29 ` Sekhar Nori
2013-07-31 5:06 ` Joel Fernandes
-- strict thread matches above, loose matches on Subject: below --
2013-08-23 19:53 Joel Fernandes
2013-08-26 10:46 ` Sekhar Nori
2013-08-26 16:52 ` Joel Fernandes
2013-08-26 19:34 ` Sekhar Nori
2013-09-06 19:13 ` Mark Jackson
2013-09-06 19:15 ` Mark Jackson
2013-09-06 19:51 ` Joel Fernandes
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=51F74688.3090702@ti.com \
--to=nsekhar@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).