From: sashiko-bot@kernel.org
To: "Jacky Chou" <jacky_chou@aspeedtech.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH net-next v3 1/6] dt-bindings: net: ftgmac100: Add AST2700 compatible
Date: Fri, 16 Oct 2026 06:47:27 +0000 [thread overview]
Message-ID: <sashiko-outbox-173881@kernel.org> (raw)
In-Reply-To: <20261015-support_ast2700-v3-1-8d7999171ac4@aspeedtech.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: net: unconditional phy-mode requirement conflicts with use-ncsi
--
commit 400bdacb7816aa92f8043666f3a7c205e84d2f56
Author: Jacky Chou <jacky_chou@aspeedtech.com>
dt-bindings: net: ftgmac100: Add AST2700 compatible
This patch adds AST2700 to the FTGMAC100 compatible list and documents its
RMII RCLK gate requirements. It mandates the phy-mode property for AST2700
and makes the Aspeed MAC compatibles standalone by removing the generic
fallback requirement.
> diff --git a/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml b/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
> index d14410018bcf6..0a376b849a916 100644
> --- a/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
> +++ b/Documentation/devicetree/bindings/net/faraday,ftgmac100.yaml
[ ... ]
> @@ -82,26 +81,35 @@ allOf:
> contains:
> enum:
> - aspeed,ast2600-mac
> + - aspeed,ast2700-mac
> then:
> properties:
> resets: true
> else:
> properties:
> resets: false
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: aspeed,ast2700-mac
> + then:
> + required:
> + - phy-mode
[Severity: Medium]
Will this unconditional requirement cause dtbs_check validation failures
for AST2700 device trees configured with NC-SI?
Looking at the driver code in drivers/net/ethernet/faraday/ftgmac100.c:
ftgmac100_probe_dt() {
...
if (of_get_property(np, "use-ncsi", NULL))
return ftgmac100_probe_ncsi(netdev, priv, pdev);
...
}
The driver explicitly bypasses PHY initialization and phy-mode validation
when use-ncsi is present. Because of this, phy-mode is conceptually
unnecessary for such configurations, but this binding schema will force
those device tree nodes to include a meaningless phy-mode property.
Could this binding be updated to only require phy-mode when use-ncsi is
not present?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261015-support_ast2700-v3-0-8d7999171ac4@aspeedtech.com?part=1
next prev parent reply other threads:[~2026-10-16 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 6:46 [PATCH net-next v3 0/6] net: ftgmac100: Add AST2700 support Jacky Chou
2026-10-15 6:46 ` [PATCH net-next v3 1/6] dt-bindings: net: ftgmac100: Add AST2700 compatible Jacky Chou
2026-10-15 19:19 ` Conor Dooley
2026-10-16 1:47 ` 回覆: " Jacky Chou
2026-10-16 6:47 ` sashiko-bot [this message]
2026-10-15 6:46 ` [PATCH net-next v3 2/6] net: ftgmac100: Add AST2700 compatible support Jacky Chou
2026-10-15 6:46 ` [PATCH net-next v3 3/6] net: ftgmac100: Enable AST2700 RMII support Jacky Chou
2026-10-15 6:46 ` [PATCH net-next v3 4/6] net: ftgmac100: Require phy-mode for AST2700 Jacky Chou
2026-10-16 6:47 ` sashiko-bot
2026-10-15 6:46 ` [PATCH net-next v3 5/6] net: ftgmac100: Add AST2700 upper DMA address support Jacky Chou
2026-10-15 6:46 ` [PATCH net-next v3 6/6] net: ftgmac100: Allow building on ARM64 Jacky Chou
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-173881@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacky_chou@aspeedtech.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