From: Conor Dooley <conor@kernel.org>
To: zjzhao@edatec.cn
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: serial: Document WK2xxx SPI UART
Date: Tue, 8 Sep 2026 18:49:25 +0100 [thread overview]
Message-ID: <20260908-user-follow-58ec6bb137e4@spud> (raw)
In-Reply-To: <20260908103129.58085-2-zjzhao@edatec.cn>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Tue, Sep 08, 2026 at 06:31:28PM +0800, zjzhao@edatec.cn wrote:
> From: Zi Jie Zhao <zjzhao@edatec.cn>
>
> Add a DT binding for the WK2xxx SPI to UART bridge ICs (WK2124, WK2132,
> WK2168, WK2202 and WK2204) from Chengdu Weikai Microelectronics (WKmic).
> Describe each UART channel with a serial@N child node carrying its serial
> and RS-485 properties. Register the wkmic vendor prefix based on the vendor
> website http://www.wkmic.com/.
>
> Differentiate compatible strings by channel count and
> register availability. Account for missing hardware flow-control and
> RS-485 registers on WK2132 and WK2202. Reject serial@2 and serial@3 on the
> two-channel members.
>
> Require the standard clocks property for the single external reference
> clock used by the chips.
>
> Signed-off-by: Zi Jie Zhao <zjzhao@edatec.cn>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-08 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 10:31 [PATCH v4 0/2] WK2xxx SPI to UART bridge driver zjzhao
2026-09-08 10:31 ` [PATCH v4 1/2] dt-bindings: serial: Document WK2xxx SPI UART zjzhao
2026-09-08 10:38 ` sashiko-bot
2026-09-08 17:49 ` Conor Dooley [this message]
2026-09-08 10:31 ` [PATCH v4 2/2] serial: wk2xxx: Add WK2xxx SPI UART driver zjzhao
2026-09-08 10:44 ` sashiko-bot
2026-09-08 17:51 ` Hugo Villeneuve
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=20260908-user-follow-58ec6bb137e4@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=zjzhao@edatec.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.