[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0df0ab4f-0032-6487-2c30-b1ccd7d9ae62@metafoo.de>
Date: Tue, 9 Aug 2016 10:39:43 +0200
From: Lars-Peter Clausen <lars@...afoo.de>
To: Shawn Lin <shawn.lin@...k-chips.com>,
Vinod Koul <vinod.koul@...el.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Huibin Hong <huibin.hong@...k-chips.com>,
Xing Zheng <zhengxing@...k-chips.com>,
devicetree@...r.kernel.org, dianders@...omium.org,
briannorris@...omium.org, Caesar Wang <wxt@...k-chips.com>,
dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH 1/3] dt/bindings: arm-pl330: add description of
arm,pl330-periph-burst
On 08/05/2016 09:25 AM, Shawn Lin wrote:
> Hi Vinod,
>
> 在 2016/8/5 11:34, Vinod Koul 写道:
>> On Fri, Aug 05, 2016 at 10:53:20AM +0800, Shawn Lin wrote:
>>> This patch adds the "arm,pl330-periph-burst" for arm-pl330 to
>>> support busrt mode.
>>
>> why should this be DT property. Only reason I can think of if some hw
>> versions support this and some won't.
>
> yes, if we want to support burst mode, both of the master(pl330) and
> client(several peripherals) should implement it, otherwise it will
> be broken when enabling.
As you said, it is up to the consumer peripheral whether it supports BURST,
SINGLE or both. So this is a per client property, but you specify this as a
a global property on the producer side.
Powered by blists - more mailing lists