From: Bjorn Andersson <andersson@kernel•org>
To: konradybcio@kernel•org, Canfeng Zhuang <canfeng.zhuang@oss•qualcomm.com>
Cc: robh@kernel•org, krzk+dt@kernel•org, conor+dt@kernel•org,
linux-arm-msm@vger•kernel.org, devicetree@vger•kernel.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH 0/2] arm64: dts: qcom: enable UARTs for robot expansion board
Date: Mon, 30 Mar 2026 11:01:14 -0500 [thread overview]
Message-ID: <177488647759.633011.5997983880216734366.b4-ty@kernel.org> (raw)
In-Reply-To: <20260327083101.1343613-1-canfeng.zhuang@oss.qualcomm.com>
On Fri, 27 Mar 2026 16:30:59 +0800, Canfeng Zhuang wrote:
> The Qualcomm Lemans EVK and Monaco EVK boards expose a mezzanine
> connector used by a motor control expansion board.
>
> This expansion board hosts an MCU running NuttX and communicates with
> Linux over UART, with all protocol handling done in userspace.
>
> This series enables the required UARTs and assigns stable serial aliases
> to ensure consistent device enumeration across platforms.
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: lemans-evk: enable UART0 for robot expansion board
commit: 0be638f326c2015ae9406f4238d9bc54b5b7a584
[2/2] arm64: dts: qcom: monaco-evk: enable UART6 for robot expansion board
commit: 74620bf0c3c6091ecd7972075f5ddeba29994407
Best regards,
--
Bjorn Andersson <andersson@kernel•org>
prev parent reply other threads:[~2026-03-30 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 8:30 [PATCH 0/2] arm64: dts: qcom: enable UARTs for robot expansion board Canfeng Zhuang
2026-03-27 8:31 ` [PATCH 1/2] arm64: dts: qcom: lemans-evk: enable UART0 " Canfeng Zhuang
2026-03-27 9:37 ` Konrad Dybcio
2026-03-27 8:31 ` [PATCH 2/2] arm64: dts: qcom: monaco-evk: enable UART6 " Canfeng Zhuang
2026-03-27 9:37 ` Konrad Dybcio
2026-03-29 11:08 ` Dmitry Baryshkov
2026-03-30 4:36 ` Canfeng Zhuang
2026-03-30 16:01 ` Bjorn Andersson [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=177488647759.633011.5997983880216734366.b4-ty@kernel.org \
--to=andersson@kernel$(echo .)org \
--cc=canfeng.zhuang@oss$(echo .)qualcomm.com \
--cc=conor+dt@kernel$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=konradybcio@kernel$(echo .)org \
--cc=krzk+dt@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=robh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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