[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <lmyugclgwb7txf3jxc3fsasp5fgu7fji5dxb2wjw4jji32omnt@rs27camphw7q>
Date: Wed, 27 Nov 2024 17:10:31 +0100
From: Sean Nyekjaer <sean@...nix.com>
To: Conor Dooley <conor@...nel.org>
Cc: Marc Kleine-Budde <mkl@...gutronix.de>,
Vincent Mailhol <mailhol.vincent@...adoo.fr>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-can@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH can-next] dt-bindings: can: tcan4x5x: add missing
required clock-names
On Wed, Nov 27, 2024 at 04:56:13PM +0100, Sean Nyekjaer wrote:
> Hi Conor,
>
> On Wed, Nov 27, 2024 at 03:50:30PM +0100, Conor Dooley wrote:
> > 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.
> >
>
> Thanks for asking the right questions :)
>
> I know the clock input is there, but it looks (to me) like the driver looks for the
> specific clock called cclk:
> https://elixir.bootlin.com/linux/v6.12/source/drivers/net/can/m_can/m_can.c#L2299
> https://elixir.bootlin.com/linux/v6.12/source/drivers/net/can/m_can/tcan4x5x-core.c#L396
Oh I really need to get my head around the dt jargon :)
Yes I'll add the clock-names to the required list for v2!
Br,
/Sean
Powered by blists - more mailing lists