linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Katsuhiro Suzuki <katsuhiro@katsuster.net>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: rockchip: use DMA channels for UARTs of TinkerBoard
Date: Sun, 15 Mar 2020 18:44:13 +0900	[thread overview]
Message-ID: <0b36bf84-0e7b-7287-a094-9fd2f33167ee@katsuster.net> (raw)
In-Reply-To: <2930126.sCcUyySgUU@diego>

Hello Heiko,

> This belongs in rk3288.dtsi, as this is definitly not board-specific, as
> the dma-uart connection is done inside the soc.
> 
> At least on arm64 (rk3328, px30, probably more) we already have the
> uart dmas in the core dtsi without any problems.
> 
> Is there any reason why you only did add it to the tinker board only?

There is no special reason. Simply I don't have and not tested on other
boards of RK3288. But I hope these DMA settings can work correctly on
other boards.

I'll resend patch for rk3288.dtsi.

Best Regards,
Katsuhiro Suzuki


On 2020/03/15 0:09, Heiko Stübner wrote:
> Hi,
> 
> Am Samstag, 14. März 2020, 15:23:27 CET schrieb Katsuhiro Suzuki:
>> This patch enables to use DMAC for all UARTs that are connected to
>> dmac_peri core for TinkerBoard.
>>
>> Only uart2 is connected different DMAC (dmac_bus_s) so keep current
>> settings on this patch.
> 
> This belongs in rk3288.dtsi, as this is definitly not board-specific, as
> the dma-uart connection is done inside the soc.
> 
> At least on arm64 (rk3328, px30, probably more) we already have the
> uart dmas in the core dtsi without any problems.
> 
> Is there any reason why you only did add it to the tinker board only?
> 
> 
> Heiko
> 
> 
>> Signed-off-by: Katsuhiro Suzuki <katsuhiro@katsuster.net>
>> ---
>>   arch/arm/boot/dts/rk3288-tinker.dtsi | 8 ++++++++
>>   1 file changed, 8 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/rk3288-tinker.dtsi b/arch/arm/boot/dts/rk3288-tinker.dtsi
>> index 312582c1bd37..6efabeaf3c6d 100644
>> --- a/arch/arm/boot/dts/rk3288-tinker.dtsi
>> +++ b/arch/arm/boot/dts/rk3288-tinker.dtsi
>> @@ -491,10 +491,14 @@ &tsadc {
>>   };
>>   
>>   &uart0 {
>> +	dmas = <&dmac_peri 1>, <&dmac_peri 2>;
>> +	dma-names = "tx", "rx";
>>   	status = "okay";
>>   };
>>   
>>   &uart1 {
>> +	dmas = <&dmac_peri 3>, <&dmac_peri 4>;
>> +	dma-names = "tx", "rx";
>>   	status = "okay";
>>   };
>>   
>> @@ -503,10 +507,14 @@ &uart2 {
>>   };
>>   
>>   &uart3 {
>> +	dmas = <&dmac_peri 7>, <&dmac_peri 8>;
>> +	dma-names = "tx", "rx";
>>   	status = "okay";
>>   };
>>   
>>   &uart4 {
>> +	dmas = <&dmac_peri 9>, <&dmac_peri 10>;
>> +	dma-names = "tx", "rx";
>>   	status = "okay";
>>   };
>>   
>>
> 
> 
> 
> 
> 


      reply	other threads:[~2020-03-15  9:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 14:23 [PATCH] ARM: dts: rockchip: use DMA channels for UARTs of TinkerBoard Katsuhiro Suzuki
2020-03-14 15:09 ` Heiko Stübner
2020-03-15  9:44   ` Katsuhiro Suzuki [this message]

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=0b36bf84-0e7b-7287-a094-9fd2f33167ee@katsuster.net \
    --to=katsuhiro@katsuster.net \
    --cc=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@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).