From: Conor Dooley <conor@kernel.org>
To: Sean Nyekjaer <sean@geanix.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
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>,
linux-can@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH can-next] dt-bindings: can: tcan4x5x: add missing required clock-names
Date: Wed, 27 Nov 2024 15:50:30 +0000 [thread overview]
Message-ID: <20241127-siberian-singular-c2b99a7fd370@spud> (raw)
In-Reply-To: <20241127-tcancclk-v1-1-5493d3f03db1@geanix.com>
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
On Wed, Nov 27, 2024 at 02:40:47PM +0100, Sean Nyekjaer wrote:
> tcan4x5x requires an external clock called cclk, add it here.
That's not what this patch is doing, the clock input is already there,
so I don't know what this patch actually accomplishes? clock-names isn't
a required property, so you can't even use it in a driver.
>
> Signed-off-by: Sean Nyekjaer <sean@geanix.com>
> ---
> Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml b/Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml
> index ff18cf7393550d1b7107b1233d8302203026579d..f3f3cbc03aec13e517552d2e29ecea1585de8e36 100644
> --- a/Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml
> +++ b/Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml
> @@ -29,6 +29,10 @@ properties:
> clocks:
> maxItems: 1
>
> + clock-names:
> + items:
> + - const: cclk
> +
> reset-gpios:
> description: Hardwired output GPIO. If not defined then software reset.
> maxItems: 1
> @@ -154,6 +158,7 @@ examples:
> can@0 {
> compatible = "ti,tcan4x5x";
> reg = <0>;
> + clock-names = "cclk";
> clocks = <&can0_osc>;
> pinctrl-names = "default";
> pinctrl-0 = <&can0_pins>;
> @@ -179,6 +184,7 @@ examples:
> can@0 {
> compatible = "ti,tcan4552", "ti,tcan4x5x";
> reg = <0>;
> + clock-names = "cclk";
> clocks = <&can0_osc>;
> pinctrl-names = "default";
> pinctrl-0 = <&can0_pins>;
>
> ---
> base-commit: e0b741bc53c94f9ae25d4140202557a0aa51b5a0
> change-id: 20241127-tcancclk-c149c0b3b050
>
> Best regards,
> --
> Sean Nyekjaer <sean@geanix.com>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-27 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 13:40 [PATCH can-next] dt-bindings: can: tcan4x5x: add missing required clock-names Sean Nyekjaer
2024-11-27 15:50 ` Conor Dooley [this message]
2024-11-27 15:56 ` Sean Nyekjaer
2024-11-27 16:10 ` Sean Nyekjaer
2024-11-27 16:18 ` Conor Dooley
2024-11-27 18:13 ` Sean Nyekjaer
2024-11-27 20:00 ` Conor Dooley
2024-11-27 20:53 ` Sean Nyekjaer
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=20241127-siberian-singular-c2b99a7fd370@spud \
--to=conor@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sean@geanix.com \
/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