From: sashiko-bot@kernel.org
To: zjzhao@edatec.cn
Cc: linux-serial@vger.kernel.org, robh@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: serial: Document WK2xxx SPI UART
Date: Fri, 09 Oct 2026 08:30:51 +0000 [thread overview]
Message-ID: <sashiko-outbox-165091@kernel.org> (raw)
In-Reply-To: <20261009082530.248219-1-zjzhao@edatec.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: missing constraints for wk2124/wk2132 flow-control and rs485
--
commit f014f512db212c81969cf531fd505916a62774fa
Author: Zi Jie Zhao <zjzhao@edatec.cn>
dt-bindings: serial: Document WK2xxx SPI UART
Add a DT binding for the WK2xxx SPI-to-UART bridge ICs (WK2124, WK2132,
WK2168, WK2212 and WK2204) from Chengdu Weikai Microelectronics (WKmic).
> diff --git a/Documentation/devicetree/bindings/serial/wkmic,wk2124.yaml b/Documentation/devicetree/bindings/serial/wkmic,wk2124.yaml
> new file mode 100644
> index 0000000000000..47a0cbdb5ca14
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/wkmic,wk2124.yaml
> @@ -0,0 +1,119 @@
> [ ... ]
> +allOf:
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - wkmic,wk2132
> + - wkmic,wk2212
> + then:
> + patternProperties:
> + "^serial@[23]$": false
[Severity: Medium]
The commit message explicitly states: "Differentiate compatible strings by
channel count and register availability. WK2124 and WK2132 lack hardware
flow-control and RS-485 registers."
However, this conditional block only differentiates the models by channel
count. Since serial.yaml and rs485.yaml are referenced unconditionally for
all serial@[0-3] nodes, device trees that configure RS-485 or hardware flow
control on WK2124 and WK2132 will silently pass schema validation despite
the hardware lacking these registers.
Should there be an additional conditional block to reject RS-485 and hardware
flow-control properties for the WK2124 and WK2132 models?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261009082530.248219-1-zjzhao@edatec.cn?part=1
next prev parent reply other threads:[~2026-10-09 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 8:24 [PATCH v5 0/2] WK2xxx SPI to UART bridge driver zjzhao
2026-10-09 8:24 ` [PATCH v5 1/2] dt-bindings: serial: Document WK2xxx SPI UART zjzhao
2026-10-09 8:30 ` sashiko-bot [this message]
2026-10-09 14:58 ` Conor Dooley
2026-10-09 8:24 ` [PATCH v5 2/2] serial: wk2xxx: Add WK2xxx SPI UART driver zjzhao
2026-10-09 8:39 ` sashiko-bot
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=sashiko-outbox-165091@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox