[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200610.170309.928494814671626769.davem@davemloft.net>
Date: Wed, 10 Jun 2020 17:03:09 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: heiko@...ech.de
Cc: kuba@...nel.org, robh+dt@...nel.org, andrew@...n.ch,
f.fainelli@...il.com, hkallweit1@...il.com, linux@...linux.org.uk,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
christoph.muellner@...obroma-systems.com,
heiko.stuebner@...obroma-systems.com
Subject: Re: [PATCH v2 2/2] net: phy: mscc: handle the clkout control on
some phy variants
From: Heiko Stuebner <heiko@...ech.de>
Date: Tue, 9 Jun 2020 15:31:40 +0200
> From: Heiko Stuebner <heiko.stuebner@...obroma-systems.com>
>
> At least VSC8530/8531/8540/8541 contain a clock output that can emit
> a predefined rate of 25, 50 or 125MHz.
>
> This may then feed back into the network interface as source clock.
> So follow the example the at803x already set and introduce a
> vsc8531,clk-out-frequency property to set that output.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@...obroma-systems.com>
> ---
> Hi Andrew,
>
> I didn't change the property yet, do you have a suggestion on
> how to name it though? Going by the other examples in the
> ethernet-phy.yamls, something like enet-phy-clock-out-frequency ?
Andrew, please help Heiko out with the naming here so we can move
forward on this patch series.
Thank you.
Powered by blists - more mailing lists