[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABb+yY3ufFhD6Gf-OqYPpa2k--c8z52fFn6VDEpmc_NgWC04XQ@mail.gmail.com>
Date: Thu, 22 Sep 2011 12:08:19 +0530
From: Jassi Brar <jassisinghbrar@...il.com>
To: Barry Song <21cnbao@...il.com>
Cc: Barry Song <Baohua.Song@....com>,
Piotr Ziecik <kosmo@...ihalf.com>,
Vinod Koul <vinod.koul@...el.com>,
Pelagicore AB <info@...agicore.com>,
Nicolas Ferre <nicolas.ferre@...el.com>,
linux-kernel@...r.kernel.org, Yong Wang <yong.y.wang@...el.com>,
dan.j.williams@...el.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] dmaengine: delete redundant chan_id and chancnt
initialization in dma drivers
On Thu, Sep 22, 2011 at 12:01 PM, Barry Song <21cnbao@...il.com> wrote:
> 2011/9/22 Jassi Brar <jassisinghbrar@...il.com>:
>> On Thu, Sep 22, 2011 at 11:11 AM, Jassi Brar <jassisinghbrar@...il.com> wrote:
>>>
>>>> client drivers can request a specific chan_id just like it can request a gpio.
>>> No dear. That's not gonna fly if we are to have common client drivers
>>> across SoCs.
>>>
>> Btw, I meant you can't simply have clients specify a channel number and
>> get the channel in a portable manner. Clients need to specify the capabilities
>> they need of the channel.
>
> if the dmac is flexible in design, what you said is right. but the
> problem is that there are some chips which actually fix one channel to
> one peripheral.
Nevertheless it is better to assume the dmac's req-signals could be hacked
to re-route at even runtime.
Also it won't work for client drivers that run the same controller on different
SoC with a different dmac.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists