From: sashiko-bot@kernel.org
To: zjzhao@edatec.cn
Cc: robh@kernel.org, conor+dt@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, 08 Sep 2026 10:38:38 +0000 [thread overview]
Message-ID: <20260908103839.61D7F1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260908103129.58085-2-zjzhao@edatec.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The binding schema and example contradict the commit message regarding RS-485 and flow-control support for the WK2132 and WK2202 variants.
--
commit 812f6612c7639102da515af64bd9d5022ac17f75
Author: Zi Jie Zhao <zjzhao@edatec.cn>
dt-bindings: serial: Document WK2xxx SPI UART
This commit adds a device tree binding schema for the WK2xxx family of SPI
to UART bridge ICs. It specifies required properties for each channel and
aims to differentiate compatible strings by channel count and register
availability, specifically noting missing RS-485 and flow-control registers
for WK2132 and WK2202.
> diff --git a/Documentation/devicetree/bindings/serial/wkmic,wk2124.yaml b/Documentation/devicetree/bindings/serial/wkmic,wk2124.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/wkmic,wk2124.yaml
[ ... ]
> +allOf:
> + - $ref: /schemas/spi/spi-peripheral-props.yaml#
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - wkmic,wk2132
> + - wkmic,wk2202
> + then:
> + patternProperties:
> + "^serial@[23]$": false
[Severity: Medium]
The commit message states that the binding accounts for missing hardware
flow-control and RS-485 registers on the WK2132 and WK2202 variants. However,
this conditional block only restricts the channel count by rejecting the
higher serial nodes. Should this block also explicitly restrict the RS-485
and hardware flow-control properties to prevent invalid configurations from
passing schema validation?
[ ... ]
> +examples:
> + - |
[ ... ]
> + serial@0 {
> + compatible = "wkmic,wk2132";
> + reg = <0>;
> + spi-max-frequency = <10000000>;
> + clocks = <&xtal>;
> + interrupt-parent = <&gpio>;
> + interrupts = <24 IRQ_TYPE_LEVEL_LOW>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + serial@0 {
> + reg = <0>;
> + };
> +
> + serial@1 {
> + reg = <1>;
> + rs485-rts-active-low;
> + linux,rs485-enabled-at-boot-time;
> + };
> + };
> + };
[Severity: Medium]
Does this example incorrectly demonstrate RS-485 capabilities on the WK2132
variant? The commit message indicates that WK2132 is missing the hardware
RS-485 registers, but this example actively applies RS-485 properties to its
serial child node.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260908103129.58085-1-zjzhao@edatec.cn?part=1
next prev parent reply other threads:[~2026-09-08 10:38 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 [this message]
2026-09-08 17:49 ` Conor Dooley
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=20260908103839.61D7F1F00A3A@smtp.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 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.