From: Quentin Schulz <quentin.schulz@cherry.de>
To: sashiko-reviews@lists.linux.dev, Quentin Schulz <foss+kernel@0leil.net>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org,
Heiko Stuebner <heiko@sntech.de>
Subject: Re: [PATCH 2/2] arm64: dts: rockchip: support CAN1-CAN2-UART4 adapter for RK3588 Jaguar
Date: Thu, 30 Jul 2026 15:44:13 +0200 [thread overview]
Message-ID: <1498d77d-e978-4bbb-8cde-4773becb9a47@cherry.de> (raw)
In-Reply-To: <20260730133511.2F6A31F00A3A@smtp.kernel.org>
On 7/30/26 3:35 PM, sashiko-bot@kernel.org wrote:
[...]
>> +
>> +/* RS232 */
>> +&uart4 {
>> + /* ST3232B only guarantees 250Kbps */
>> + max-speed = <250000>;
>> + status = "okay";
>> +};
>
> [Severity: Medium]
> Is the max-speed property effective when placed directly on the UART
> controller node?
>
> According to the device tree bindings (serial-peripheral-props.yaml),
> max-speed is meant for serial peripherals (child nodes of the UART).
> Standard kernel UART drivers typically do not parse or enforce the
> max-speed property on the controller node itself.
>
> Will this actually limit the baud rate, or will it be ignored by the driver?
>
Forgot to check when porting from downstream. max-speed is seldom used
in Linux kernel and it is indeed specific to devices on UART as does a
quick "git grep max-speed drivers/" tell me. I'll send a v2 with that
property removed but will leave a few days/weeks for comments, there's
no hurry. Sorry for the noise.
Cheers,
Quentin
prev parent reply other threads:[~2026-07-30 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 13:18 [PATCH 0/2] arm64: dts: rockchip: support CAN1-CAN2-UART4 adapter for RK3588 Jaguar + enable CAN0 Quentin Schulz
2026-07-30 13:18 ` [PATCH 1/2] arm64: dts: rockchip: enable CAN0 on RK3588 Jaguar Quentin Schulz
2026-07-30 13:34 ` sashiko-bot
2026-07-30 13:18 ` [PATCH 2/2] arm64: dts: rockchip: support CAN1-CAN2-UART4 adapter for " Quentin Schulz
2026-07-30 13:35 ` sashiko-bot
2026-07-30 13:44 ` Quentin Schulz [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=1498d77d-e978-4bbb-8cde-4773becb9a47@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=foss+kernel@0leil.net \
--cc=heiko@sntech.de \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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