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: Wed, 13 Nov 2024 00:25:28 +0100 [thread overview]
Message-ID: <0eb19e4daf2cdf3d4a04935876c3d3b0@manjaro.org> (raw)
In-Reply-To: <CA+GksrJjDPve29Vh7ZFhM+JFp058xmXZAPeuLuFth7v=JeiH2w@mail.gmail.com>
Hello Tamas,
On 2024-11-12 22:04, Tamás Szűcs wrote:
> On Tue, Nov 12, 2024 at 4:07 PM Dragan Simic <dsimic@manjaro.org>
> wrote:
>> 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?
>
> UART8 is supposed to be used for any radio module connected to the M2E
> connector.
> It will typically be responsible for Bluetooth or BLE but it could be
> 802.15.4 or whatever. In any case, all wanting to use it will need the
> uart8 node enabled.
I see, but I'm still guessing what's the actual use of enabling the
UART8 when it will remain pretty much useless without the additional
DT configuration, such as in the WiFi+Bluetooth DT overlay that Jonas
sent a bit earlier?
I think that the UART8 should be enabled together with something that
actually makes use of it, which in this case unfortunately cannot be
automatically detected and configured, so it belongs to a DT overlay.
I'll get back to this in my next response.
>> With that in mind, I see very little sense in just enabling the UART,
>> without defining the entire Bluetooth interface, which AFAIK produces
>
> Defining a bluetooth node would hardwire idiosyncrasies of a given
> radio module's Bluetooth core. Sure you could add a sleep clock, all
> kind of sideband signals for wakeups, reset, power down, etc. But hey,
> some will use them, some won't. I think it's undesirable and
> unnecessary. You can hciattach from here and most will work just like
> that. Tighter integration or anything special, module specific on top
> should be handled individially, on a case-by-case basis. This is a dev
> board after all. I say trick of all trades.
>
>> nasty looking error messages in the kernel log when there's actually
>> nothing connected to the UART.
>
> My dmesg is clean as a whistle
> root@rock-3b:~# dmesg | grep -E 'fe6c0000|ttyS0'
> [ 0.344818] fe6c0000.serial: ttyS0 at MMIO 0xfe6c0000 (irq = 26,
> base_baud = 1500000) is a 16550A
> What kind of nasty errors do you recall?
Those would be the kernel error messages produced with the Bluetooth
DT configuration in place, but with no SDIO module installed.
_______________________________________________
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-13 0:31 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
2024-11-12 21:04 ` Tamás Szűcs
2024-11-12 22:21 ` Jonas Karlman
2024-11-12 23:25 ` Dragan Simic [this message]
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=0eb19e4daf2cdf3d4a04935876c3d3b0@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