[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c1931bd6-1a9f-4de5-ab0a-d940e2cd062b@linaro.org>
Date: Thu, 22 Feb 2024 19:15:55 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Yang Xiwen <forbidden405@...look.com>,
Yisen Zhuang <yisen.zhuang@...wei.com>, Salil Mehta
<salil.mehta@...wei.com>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>, Russell King <linux@...linux.org.uk>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH net-next v3 2/6] dt-bindings: net: hisilicon-femac-mdio:
convert to YAML
On 21/02/2024 12:24, Yang Xiwen wrote:
> On 2/21/2024 4:12 PM, Krzysztof Kozlowski wrote:
>> On 19/02/2024 20:57, Yang Xiwen via B4 Relay wrote:
>>> From: Yang Xiwen <forbidden405@...look.com>
>>>
>>> Also mark the clock optional
>> Why? Your commit msg must provide rationale. Clocks are rarely optional
>> signals, so this looks wrong.
>
>
> Well. I don't know too much about the hardware either. I think the clock
> can be either shared with MAC controller or completely non-existent in
> hardware.
>
>
> But from the driver side, the clock must be stripped from MDIO bus node.
> The clocks must be controlled entirely within MAC controller driver. Do
> I need to mention it in this commit too?
>
>
> Actually I've never seen anything like "MDIO bus clock" in the
> datasheet. The MDIO bus and MAC controller are activated simultaneously.
> So I think removing this clock entirely is also acceptable.
None of these are arguments to make the clock optional. The last one is
an argument to drop clock entirely.
Best regards,
Krzysztof
Powered by blists - more mailing lists