From: sashiko-bot@kernel.org
To: lizhi2@eswincomputing.com
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v10 1/4] dt-bindings: ethernet: eswin: relax internal delay model to range-based constraints
Date: Wed, 08 Jul 2026 06:43:22 +0000 [thread overview]
Message-ID: <20260708064323.73A661F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260707064131.1282-1-lizhi2@eswincomputing.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] DT Binding and Driver mismatch: relaxed delay properties cause probe failure.
--
--- Patch [1]: [PATCH net-next v10 1/4] dt-bindings: ethernet: eswin: relax internal delay model to range-based constraints ---
commit 3dceaf931915c24887e11e00c0d85cb45cef4d39
Author: Zhi Li <lizhi2@eswincomputing.com>
dt-bindings: ethernet: eswin: relax internal delay model to range-based constraints
This commit relaxes internal delay constraints for the EIC7700 Ethernet
binding, replacing fixed enumerations with range-based definitions. It also
makes the rx-internal-delay-ps and tx-internal-delay-ps properties optional.
> diff --git a/Documentation/devicetree/bindings/net/eswin,eic7700-eth.yaml b/Documentation/devicetree/bindings/net/eswin,eic7700-eth.yaml
> index 65882ff79d8d7..4e02fedae5c67 100644
> --- a/Documentation/devicetree/bindings/net/eswin,eic7700-eth.yaml
> +++ b/Documentation/devicetree/bindings/net/eswin,eic7700-eth.yaml
[ ... ]
> @@ -105,8 +109,6 @@ required:
> - phy-mode
> - resets
> - reset-names
> - - rx-internal-delay-ps
> - - tx-internal-delay-ps
[Severity: High]
With this change, the DT schema makes these properties optional. However, does
the eic7700-qos-eth driver still require them?
Looking at eic7700_dwmac_probe(), it appears to return an error if these
properties are missing:
drivers/net/ethernet/stmicro/stmmac/dwmac-eic7700.c:eic7700_dwmac_probe() {
...
} else {
return dev_err_probe(&pdev->dev, -EINVAL,
"missing required property rx-internal-delay-ps\n");
}
...
} else {
return dev_err_probe(&pdev->dev, -EINVAL,
"missing required property tx-internal-delay-ps\n");
}
...
}
Will this cause the probe to fail if a device tree omits these properties,
as permitted by the updated schema?
> - eswin,hsp-sp-csr
>
> unevaluatedProperties: false
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260707064033.1265-1-lizhi2@eswincomputing.com?part=1
next prev parent reply other threads:[~2026-07-08 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 6:40 [PATCH net-next v10 0/4] net: stmmac: eic7700: add eth1 variant support and update delay bindings lizhi2
2026-07-07 6:41 ` [PATCH net-next v10 1/4] dt-bindings: ethernet: eswin: relax internal delay model to range-based constraints lizhi2
2026-07-08 6:43 ` sashiko-bot [this message]
2026-07-10 2:46 ` 李志
2026-07-07 6:41 ` [PATCH net-next v10 2/4] dt-bindings: ethernet: eswin: add EIC7700 eth1 RX clock inversion variant lizhi2
2026-07-08 6:43 ` sashiko-bot
2026-07-07 6:42 ` [PATCH net-next v10 3/4] net: stmmac: eic7700: make RGMII delay properties optional lizhi2
2026-07-07 6:42 ` [PATCH net-next v10 4/4] net: stmmac: eic7700: add support for eth1 clock inversion variant lizhi2
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=20260708064323.73A661F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lizhi2@eswincomputing.com \
--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