[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220510133928.6a0710dd@kernel.org>
Date: Tue, 10 May 2022 13:39:28 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Josua Mayer <josua@...id-run.com>
Cc: netdev@...r.kernel.org, alvaro.karsz@...id-run.com,
Michael Hennerich <michael.hennerich@...log.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Alexandru Ardelean <alexandru.ardelean@...log.com>
Subject: Re: [PATCH v4 1/3] dt-bindings: net: adin: document phy clock
output properties
On Mon, 9 May 2022 17:36:33 +0300 Josua Mayer wrote:
> + adi,phy-output-clock:
> + description: Select clock output on GP_CLK pin. Three clocks are available:
> + A 25MHz reference, a free-running 125MHz and a recovered 125MHz.
> + The phy can also automatically switch between the reference and the
> + respective 125MHz clocks based on its internal state.
> + $ref: /schemas/types.yaml#/definitions/string
> + enum:
> + - 25mhz-reference
> + - 125mhz-free-running
> + - 125mhz-recovered
> + - adaptive-free-running
> + - adaptive-recovered
I'm still not convinced that exposing the free running vs recovered
distinction from the start is a good idea. Intuitively it'd seem that
it's better to use the recovered clock to feed the wire side of the MAC,
this patch set uses the free running. So I'd personally strip the last
part off and add it later if needed.
But I won't fuss, if we get an ack from one of the PHY maintainers -
I'll merge as is.
Andrew?
Powered by blists - more mailing lists