devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Andrew Lunn <andrew@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>,
	"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	imx@lists.linux.dev
Subject: Re: [PATCH 1/1] dt-bindings: net: dsa: nxp,sja1105: Add optional clock
Date: Tue, 14 Oct 2025 23:07:01 +0300	[thread overview]
Message-ID: <20251014200701.owvbmsfcibwseqfr@skbuf> (raw)
In-Reply-To: <20251010183418.2179063-1-Frank.Li@nxp.com>

On Fri, Oct 10, 2025 at 02:34:17PM -0400, Frank Li wrote:
> Add optional clock for OSC_IN and fix the below CHECK_DTBS warnings:
>   arch/arm/boot/dts/nxp/imx/imx6qp-prtwd3.dtb: switch@0 (nxp,sja1105q): Unevaluated properties are not allowed ('clocks' was unexpected)
> 
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
>  Documentation/devicetree/bindings/net/dsa/nxp,sja1105.yaml | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/net/dsa/nxp,sja1105.yaml b/Documentation/devicetree/bindings/net/dsa/nxp,sja1105.yaml
> index e9dd914b0734c..607b7fe8d28ee 100644
> --- a/Documentation/devicetree/bindings/net/dsa/nxp,sja1105.yaml
> +++ b/Documentation/devicetree/bindings/net/dsa/nxp,sja1105.yaml
> @@ -41,6 +41,9 @@ properties:
>        therefore discouraged.
>      maxItems: 1
>  
> +  clocks:
> +    maxItems: 1
> +
>    spi-cpha: true
>    spi-cpol: true
>  
> -- 
> 2.34.1
> 

Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>

with the comment that you might want to add clk_prepare_enable() driver
support for it too. Someone who specifies a clock which isn't fixed
might be taken by surprise by the missing driver logic.

  parent reply	other threads:[~2025-10-14 20:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 18:34 [PATCH 1/1] dt-bindings: net: dsa: nxp,sja1105: Add optional clock Frank Li
2025-10-14 18:02 ` Conor Dooley
2025-10-14 18:12   ` Conor Dooley
2025-10-14 19:02     ` Jakub Kicinski
2025-10-14 19:35       ` Conor Dooley
2025-10-14 20:40         ` Jakub Kicinski
2025-10-14 20:48         ` Rob Herring
2025-10-15  1:13           ` Jakub Kicinski
2025-10-15 11:53             ` Rob Herring
2025-10-15 12:09               ` Andrew Lunn
2025-10-15 14:25               ` Jakub Kicinski
2025-10-15 17:32                 ` Rob Herring
2025-10-15 17:53                   ` Jakub Kicinski
2025-10-15 21:56                     ` Conor Dooley
2025-10-14 20:07 ` Vladimir Oltean [this message]
2025-10-15 16:00 ` patchwork-bot+netdevbpf

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=20251014200701.owvbmsfcibwseqfr@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=imx@lists.linux.dev \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.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;
as well as URLs for NNTP newsgroup(s).