From: Dragan Simic <dsimic@manjaro.org>
To: "Tamás Szűcs" <tszucs@linux.com>
Cc: Jonas Karlman <jonas@kwiboo.se>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, FUKAUMI Naoki <naoki@radxa.com>,
Chukun Pan <amadeus@jmu.edu.cn>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Enable UART8 on rock-3b
Date: Tue, 12 Nov 2024 16:07:10 +0100 [thread overview]
Message-ID: <9330ebb370780c001fd2aaee49aec9e8@manjaro.org> (raw)
In-Reply-To: <CA+GksrJLpeU8x-kjR1Ng3ySf+giiufCsJuBssng9qoX1PjAunA@mail.gmail.com>
Hello Tamas,
On 2024-11-12 15:35, Tamás Szűcs wrote:
> I agree; it's not possible to tell if the user will use a PCIe/USB,
> PCIe/UART, SDIO/UART, perhaps USB/UART device, or any other HIF
> combination. The way I see it is UART8 is hardwired to the M2E, so
> there is a reasonable expectation that it should work too if need be.
Please correct me if I'm wrong, but isn't this UART supposed to be
used for the Bluetooth part of an SDIO WiFi + Bluetooth module, in
form of a non-standard M.2 module that Radxa sells?
With that in mind, I see very little sense in just enabling the UART,
without defining the entire Bluetooth interface, which AFAIK produces
nasty looking error messages in the kernel log when there's actually
nothing connected to the UART.
As a side note, please use inline replying. [*]
[*] https://en.wikipedia.org/wiki/Posting_style
> On Mon, Nov 11, 2024 at 8:12 PM Jonas Karlman <jonas@kwiboo.se> wrote:
>>
>> Hi Tamás,
>>
>> On 2024-11-11 19:17, Tamás Szűcs wrote:
>> > Enable UART lines on Radxa ROCK 3 Model B M.2 Key E.
>> >
>> > Signed-off-by: Tamás Szűcs <tszucs@linux.com>
>> > ---
>> > arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts b/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts
>> > index b7527ba418f7..61d4ba2d312a 100644
>> > --- a/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts
>> > +++ b/arch/arm64/boot/dts/rockchip/rk3568-rock-3b.dts
>> > @@ -732,7 +732,7 @@ &uart8 {
>> > pinctrl-names = "default";
>> > pinctrl-0 = <&uart8m0_xfer &uart8m0_ctsn &uart8m0_rtsn>;
>> > uart-has-rtscts;
>> > - status = "disabled";
>> > + status = "okay";
>>
>> This should probably be enabled using an dt-overlay, there is no UART
>> device embedded on the board and the reason I left it disabled in
>> original board DT submission.
>>
>> On second thought maybe they should be enabled, think PCIe and USB
>> lines
>> on the M.2 Key E is already enabled by default. I probably only tested
>> with a pcie/usb wifi/bt card and not a sido/uart wifi/bt card.
>>
>> > };
>> >
>> > &usb_host0_ehci {
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-11-12 15:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 18:17 [PATCH 0/3] arm64: dts: rockchip: rock-3b TF + M2E updates Tamás Szűcs
2024-11-11 18:17 ` [PATCH 1/3] arm64: dts: rockchip: Add supported UHS-I rates to sdmmc0 on rock-3b Tamás Szűcs
2024-11-11 19:00 ` Jonas Karlman
2024-11-12 14:36 ` Tamás Szűcs
2024-11-12 22:37 ` Jonas Karlman
2024-11-13 10:24 ` Tamás Szűcs
2024-11-11 18:17 ` [PATCH 2/3] arm64: dts: rockchip: Enable sdmmc2 on rock-3b and set it up for SDIO devices Tamás Szűcs
2024-11-11 19:06 ` Jonas Karlman
2024-11-12 4:41 ` Dragan Simic
2024-11-12 14:35 ` Tamás Szűcs
2024-11-12 15:15 ` Dragan Simic
2024-11-12 21:05 ` Tamás Szűcs
2024-11-12 23:38 ` Dragan Simic
2024-11-13 10:24 ` Tamás Szűcs
2024-11-13 10:44 ` Dragan Simic
2024-11-13 11:17 ` Tamás Szűcs
2024-11-13 13:12 ` Dragan Simic
2024-11-11 18:17 ` [PATCH 3/3] arm64: dts: rockchip: Enable UART8 on rock-3b Tamás Szűcs
2024-11-11 19:12 ` Jonas Karlman
2024-11-12 14:35 ` Tamás Szűcs
2024-11-12 15:07 ` Dragan Simic [this message]
2024-11-12 21:04 ` Tamás Szűcs
2024-11-12 22:21 ` Jonas Karlman
2024-11-12 23:25 ` Dragan Simic
2024-11-13 10:24 ` Tamás Szűcs
2024-11-13 10:38 ` Dragan Simic
2024-11-13 11:17 ` Tamás Szűcs
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=9330ebb370780c001fd2aaee49aec9e8@manjaro.org \
--to=dsimic@manjaro.org \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=robh@kernel.org \
--cc=tszucs@linux.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