From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: imx@lists.linux.dev, krzk+dt@kernel.org,
devicetree@vger.kernel.org, Frank.Li@kernel.org, robh@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH 1/1] dt-bindings: trivial-devices: add fsl,mc1323
Date: Fri, 15 May 2026 16:51:24 +0000 [thread overview]
Message-ID: <20260515165125.26C53C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260515163959.1948799-1-Frank.Li@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Miscategorization of the fsl,mc1323 complex network transceiver as a trivial device.
--
commit 21d3bd06bf5d8d09338547376852b755873e842b
Author: Frank Li <Frank.Li@nxp.com>
dt-bindings: trivial-devices: add fsl,mc1323
This commit adds support for the Freescale 2.4 GHz IEEE 802.15.4/ZigBee
mc1323 by listing it as a compatible string in the trivial-devices schema.
> diff --git a/Documentation/devicetree/bindings/trivial-devices.yaml b/Documentation/devicetree/bindings/trivial-devices.yaml
> index 23fd4513933a4..28b059c858dd1 100644
> --- a/Documentation/devicetree/bindings/trivial-devices.yaml
> +++ b/Documentation/devicetree/bindings/trivial-devices.yaml
[ ... ]
> @@ -127,6 +127,8 @@ properties:
> - domintech,dmard09
> # DMARD10: 3-axis Accelerometer
> - domintech,dmard10
> + # Freescale 2.4 GHz IEEE® 802.15.4/ZigBee
> + - fsl,mc1323
The trivial-devices.yaml binding is intended for simple SPI/I2C devices and
strictly enforces additionalProperties: false. Since the Freescale MC1323 is
a complex System-on-Chip that includes an MCU and a transceiver, wouldn't it
require additional properties like reset lines, regulators, clocks, or MAC
address configurations?
Adding it here might restrict the binding and cause future schema validation
failures when someone attempts to properly define those necessary hardware
properties.
Should this device have a dedicated binding schema instead of being
categorized as a trivial device?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260515163959.1948799-1-Frank.Li@oss.nxp.com?part=1
prev parent reply other threads:[~2026-05-15 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 16:39 [PATCH 1/1] dt-bindings: trivial-devices: add fsl,mc1323 Frank.Li
2026-05-15 16:51 ` sashiko-bot [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=20260515165125.26C53C2BCB3@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--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