From: Diederik de Haas <didi.debian@cknow.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Maximilian Weigand <mweigand@mweigand.net>,
Dragan Simic <dsimic@manjaro.org>,
Diederik de Haas <didi.debian@cknow.org>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Chris Morgan <macromorgan@hotmail.com>,
Andy Yan <andyshrk@163.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Chukun Pan <amadeus@jmu.edu.cn>,
Furkan Kardame <f.kardame@manjaro.org>,
Michael Riesch <michael.riesch@wolfvision.net>,
Shengyu Qu <wiagn233@outlook.com>
Subject: arm64: dts: rockchip: Add dma-names to uart-bluetooth rk3566 devices
Date: Fri, 5 Jul 2024 18:22:12 +0200 [thread overview]
Message-ID: <20240705163004.29678-2-didi.debian@cknow.org> (raw)
This is a single patch which adds the dma-names property to the uart
node with a bluetooth subnode on Pine64's rk356x devices.
But that property can potentially be added to several other devices, but
I have zero familiarity with them or their community, so I choose not to
add it to those devices, but inform people via this cover letter.
The dts/dtsi files I found as potential candidates are:
- rk3566-anbernic-rgxx3.dtsi
- rk3566-box-demo.dts
- rk3566-powkiddy-rk2023.dtsi
- rk3566-powkiddy-x55.dts
- rk3566-radxa-cm3.dtsi
- rk3566-rock-3c.dts
- rk3566-roc-pc.dts
- rk3568-rock-3a.dts
next reply other threads:[~2024-07-05 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 16:22 Diederik de Haas [this message]
2024-07-05 16:22 ` [PATCH] arm64: dts: rockchip: Add dma-names to uart1 on Pine64 rk3566 devices Diederik de Haas
2024-07-08 14:28 ` Heiko Stuebner
2024-07-08 16:05 ` arm64: dts: rockchip: Add dma-names to uart-bluetooth " Chris Morgan
2024-07-08 16:35 ` Diederik de Haas
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=20240705163004.29678-2-didi.debian@cknow.org \
--to=didi.debian@cknow.org \
--cc=amadeus@jmu.edu.cn \
--cc=andyshrk@163.com \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=f.kardame@manjaro.org \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=michael.riesch@wolfvision.net \
--cc=mweigand@mweigand.net \
--cc=wiagn233@outlook.com \
/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