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 21:59:04 +0530 [thread overview]
Message-ID: <51F7E9D0.1080107@ti.com> (raw)
In-Reply-To: <51F73738.6080901@ti.com>
On 7/30/2013 9:17 AM, Joel Fernandes wrote:
>>> diff --git a/arch/arm/common/edma.c b/arch/arm/common/edma.c
>>> index a432e6c..765d578 100644
>>> --- a/arch/arm/common/edma.c
>>> +++ b/arch/arm/common/edma.c
>>> + } else {
>>> + for (; i < pdev->num_resources; i++) {
>>> + if ((pdev->resource[i].flags & IORESOURCE_DMA) &&
>>> + (int)pdev->resource[i].start >= 0) {
>>> + ctlr = EDMA_CTLR(pdev->resource[i].start);
>>> + clear_bit(EDMA_CHAN_SLOT(
>>> + pdev->resource[i].start),
>>> + edma_cc[ctlr]->edma_unused);
>>> + }
>>
>> So there is very little in common between OF and non-OF versions of this
>> function. Why not have two different versions of this function for the
>> two cases? The OF version can reside under the CONFIG_OF conditional
>> already in use in the file. This will also save you the ugly line breaks
>> you had to resort to due to too deep indentation.
>
> Actually those line breaks are not necessary and wouldn't result in
> compilation errors. I was planning to drop them. I'll go ahead and split
> it out anyway, now that also the OF version of the function is going to
> be bit longer if we use the of_parse functions.
>
> Thanks for your review,
It turns out, I gave a bad idea. What I suggested will break the case of
non-DT boot with CONFIG_OF enabled. So what you had was fine. May be
just return from "if (dev->of_node)" so you don't need to have an else
block and can save on the indentation.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-07-30 16:29 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
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 [this message]
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=51F7E9D0.1080107@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).