From: Dragan Simic <dsimic@manjaro.org>
To: Philipp Puschmann <p.puschmann@pironex.com>
Cc: Diederik de Haas <didi.debian@cknow.org>,
linux-rockchip@lists.infradead.org, robh@kernel.org,
krzk+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: Add uart dma names to the SoC dtsi for RK356x
Date: Wed, 10 Jul 2024 16:56:04 +0200 [thread overview]
Message-ID: <9af7bd0db5bc5fd23cfeb121b78bbdc1@manjaro.org> (raw)
In-Reply-To: <72e38433-1ed4-460c-9f69-db26b673c441@pironex.com>
Hello Philipp,
On 2024-07-10 12:20, Philipp Puschmann wrote:
> Am 10.07.24 um 12:02 schrieb Diederik de Haas:
>> On Wednesday, 10 July 2024 11:33:56 CEST Philipp Puschmann wrote:
>>> DMA names are required by of_dma_request_slave_channel function that
>>> is
>>> called during uart probe. So to enable DMA for uarts add the names as
>>> in
>>> the RK3568 TRM.
>>
>> Setting it on channels without flow control apparently causes issues.
>> See
>>
>> https://lore.kernel.org/linux-rockchip/20240628120130.24076-1-didi.debian@cknow.org/
>
> Ah is see. The only problem that i have is to enable/disable dmas by
> having or not having
> dma-names properties, where the latter case is followed by kernel
> error messages. That
> is very counterintuitive. Maybe a explicit boolean like dma-broken
> would be better. That
> could be set on dtsi level as default and deleted on board dts if
> wanted. With such
> a boolean we could also prevent the misleading "dma-names property of"
> error message
> and replace it with a hint that dma is disabled on purpose.
From what I've read in the prior discussions, this seems like a driver
issue, so the driver should be fixed instead.
>>
>>> Signed-off-by: Philipp Puschmann <p.puschmann@pironex.com>
>>> ---
>>> arch/arm64/boot/dts/rockchip/rk356x.dtsi | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
>>> b/arch/arm64/boot/dts/rockchip/rk356x.dtsi index
>>> d8543b5557ee..4ae40661ca6a
>>> 100644
>>> --- a/arch/arm64/boot/dts/rockchip/rk356x.dtsi
>>> +++ b/arch/arm64/boot/dts/rockchip/rk356x.dtsi
>>> @@ -489,6 +489,7 @@ uart0: serial@fdd50000 {
>>> clocks = <&pmucru SCLK_UART0>, <&pmucru PCLK_UART0>;
>>> clock-names = "baudclk", "apb_pclk";
>>> dmas = <&dmac0 0>, <&dmac0 1>;
>>> + dma-names = "tx", "rx";
>>> pinctrl-0 = <&uart0_xfer>;
>>> pinctrl-names = "default";
>>> reg-io-width = <4>;
>>> @@ -1389,6 +1390,7 @@ uart1: serial@fe650000 {
>>> clocks = <&cru SCLK_UART1>, <&cru PCLK_UART1>;
>>> clock-names = "baudclk", "apb_pclk";
>>> dmas = <&dmac0 2>, <&dmac0 3>;
>>> + dma-names = "tx", "rx";
>>> pinctrl-0 = <&uart1m0_xfer>;
>>> pinctrl-names = "default";
>>> reg-io-width = <4>;
>>> ...
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-07-10 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 9:33 [PATCH] arm64: dts: rockchip: Add uart dma names to the SoC dtsi for RK356x Philipp Puschmann
2024-07-10 10:02 ` Diederik de Haas
2024-07-10 10:20 ` Philipp Puschmann
2024-07-10 10:53 ` Diederik de Haas
2024-07-10 11:58 ` Philipp Puschmann
2024-07-10 14:56 ` Dragan Simic [this message]
2024-07-10 15:14 ` Philipp Puschmann
2024-07-10 15:37 ` Dragan Simic
2024-07-10 18:05 ` Alex Bee
2024-07-10 18:21 ` Dragan Simic
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=9af7bd0db5bc5fd23cfeb121b78bbdc1@manjaro.org \
--to=dsimic@manjaro.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=krzk+dt@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=p.puschmann@pironex.com \
--cc=robh@kernel.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).