Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jacky Chou <jacky_chou@aspeedtech.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	Andrew Jeffery <andrew@codeconstruct.com.au>,
	Andrew Jeffery <andrew@aj.id.au>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] dt-bindings: net: aspeed: add AST2700 MDIO compatible
Date: Wed, 19 Nov 2025 18:41:05 +0000	[thread overview]
Message-ID: <20251119-gooey-wifi-413598a8a1d7@spud> (raw)
In-Reply-To: <20251117-aspeed_mdio_ast2700-v1-1-8ecb0032f554@aspeedtech.com>

[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]

On Mon, Nov 17, 2025 at 03:30:18PM +0800, Jacky Chou wrote:
> Add "aspeed,ast2700-mdio" compatible to the binding schema with a fallback
> to "aspeed,ast2600-mdio".
> 
> Although the MDIO controller on AST2700 is functionally the same as the
> one on AST2600, it's good practice to add a SoC-specific compatible for
> new silicon. This allows future driver updates to handle any 2700-specific
> integration issues without requiring devicetree changes or complex
> runtime detection logic.
> 
> For now, the driver continues to bind via the existing
> "aspeed,ast2600-mdio" compatible, so no driver changes are needed.
> 
> Signed-off-by: Jacky Chou <jacky_chou@aspeedtech.com>
> ---
>  Documentation/devicetree/bindings/net/aspeed,ast2600-mdio.yaml | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/net/aspeed,ast2600-mdio.yaml b/Documentation/devicetree/bindings/net/aspeed,ast2600-mdio.yaml
> index d6ef468495c5..1c90e7c15a44 100644
> --- a/Documentation/devicetree/bindings/net/aspeed,ast2600-mdio.yaml
> +++ b/Documentation/devicetree/bindings/net/aspeed,ast2600-mdio.yaml
> @@ -13,13 +13,19 @@ description: |+
>    The ASPEED AST2600 MDIO controller is the third iteration of ASPEED's MDIO
>    bus register interface, this time also separating out the controller from the
>    MAC.
> +  The ASPEED AST2700 MDIO controller is similar to the AST2600's.

This statement disagrees with your commit message that claims
functionally identical, and implies that the 2700 supports some extra
features or whatever.
I think I'd drop this entirely from the patch, rather than try to reword
it. Remove it and then:
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: changes-requested

>  allOf:
>    - $ref: mdio.yaml#
>  
>  properties:
>    compatible:
> -    const: aspeed,ast2600-mdio
> +    oneOf:
> +      - const: aspeed,ast2600-mdio
> +      - items:
> +          - enum:
> +              - aspeed,ast2700-mdio
> +          - const: aspeed,ast2600-mdio
>  
>    reg:
>      maxItems: 1
> 
> ---
> base-commit: c9dfb92de0738eb7fe6a591ad1642333793e8b6e
> change-id: 20251117-aspeed_mdio_ast2700-aa089c4f0474
> 
> Best regards,
> -- 
> Jacky Chou <jacky_chou@aspeedtech.com>
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-19 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17  7:30 [PATCH net-next] dt-bindings: net: aspeed: add AST2700 MDIO compatible Jacky Chou
2025-11-19 18:41 ` Conor Dooley [this message]
2025-11-20  3:20   ` 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=20251119-gooey-wifi-413598a8a1d7@spud \
    --to=conor@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@aj.id.au \
    --cc=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=jacky_chou@aspeedtech.com \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    /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