From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Jie Luo <quic_luoj@quicinc.com>,
agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, robert.marko@sartura.hr,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_srichara@quicinc.com
Subject: Re: [PATCH v4 5/5] dt-bindings: net: ipq4019-mdio: Document ipq5332 platform
Date: Tue, 26 Dec 2023 12:21:56 +0000 [thread overview]
Message-ID: <20231226-twine-smolder-713cb81fa411@spud> (raw)
In-Reply-To: <58dde1a7-ed4a-442c-bb5c-c3f6d926fb7e@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1898 bytes --]
On Tue, Dec 26, 2023 at 10:28:09AM +0100, Krzysztof Kozlowski wrote:
> On 26/12/2023 08:25, Jie Luo wrote:
> >>> + qcom,cmn-ref-clock-frequency:
> >>> + $ref: /schemas/types.yaml#/definitions/uint32
> >>> + enum:
> >>> + - 25000000
> >>> + - 31250000
> >>> + - 40000000
> >>> + - 48000000
> >>> + - 50000000
> >>> + - 96000000
> >>> + default: 48000000
> >>> + description: |
> >>> + The reference clock source of CMN PLL block is selectable, the
> >>> + reference clock source can be from wifi module or the external
> >>> + xtal, the reference clock frequency 48MHZ can be from internal
> >>> + wifi or the external xtal, if absent, the internal 48MHZ is used,
> >>> + if the 48MHZ is specified, which means the external 48Mhz is used.
> >>
> >> This does not resolve mine and Conor's concerns from previous version.
> >> External clocks are defined as clock inputs.
> >
> > No matter the external or internal reference clock, they are the clock
> > source selection for CMN, there are only 48MHZ can be external or
> > internal, other clocks have the different clock rate, so the internal
> > 48MHZ reference clock can be implied when the
> > "qcom,cmn-ref-clock-frequency" is not defined, which is suggested by
> > Conor in the previous
> > comments.
>
> I don't think he proposed it, but maybe I missed some message (care to
> point me to his message where he agreed on usage of
> qcom,cmn-ref-clock-frequency?). I am pretty sure we both stayed on the
> same page, that the presence of clocks defines choice of internal clock.
> This property should go away.
Exactly, I wanted this property to be removed. My suggestion was about
defaulting to the internal clock when the "clocks" property did not
contain the cmn ref clock.
> It is tiring to keep discussing this.
Yup.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-26 12:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-25 8:44 [PATCH v4 0/5] support " Luo Jie
2023-12-25 8:44 ` [PATCH v4 1/5] net: mdio: ipq4019: move eth_ldo_rdy before MDIO bus register Luo Jie
2023-12-28 9:49 ` Konrad Dybcio
2023-12-30 3:15 ` Jie Luo
2024-01-02 17:24 ` Russell King (Oracle)
2024-01-03 13:27 ` Jie Luo
2023-12-25 8:44 ` [PATCH v4 2/5] net: mdio: ipq4019: enable the SoC uniphy clocks for ipq5332 platform Luo Jie
2024-01-03 9:48 ` Bryan O'Donoghue
2024-01-03 13:25 ` Jie Luo
2023-12-25 8:44 ` [PATCH v4 3/5] net: mdio: ipq4019: configure CMN PLL clock for ipq5332 Luo Jie
2024-01-03 9:50 ` Bryan O'Donoghue
2024-01-03 13:06 ` Jie Luo
2023-12-25 8:44 ` [PATCH v4 4/5] net: mdio: ipq4019: support MDIO clock frequency divider Luo Jie
2023-12-25 8:44 ` [PATCH v4 5/5] dt-bindings: net: ipq4019-mdio: Document ipq5332 platform Luo Jie
2023-12-25 10:29 ` Krzysztof Kozlowski
2023-12-26 7:25 ` Jie Luo
2023-12-26 9:28 ` Krzysztof Kozlowski
2023-12-26 12:21 ` Conor Dooley [this message]
2023-12-26 13:14 ` Jie Luo
2023-12-26 13:19 ` Krzysztof Kozlowski
2023-12-28 7:36 ` Jie Luo
2023-12-26 13:06 ` Jie Luo
2023-12-26 13:18 ` Krzysztof Kozlowski
2023-12-28 7:38 ` Jie Luo
2024-01-04 7:47 ` Krzysztof Kozlowski
2024-01-04 10:06 ` Jie Luo
2024-01-01 23:01 ` [PATCH v4 0/5] support " Sergey Ryazanov
2024-01-03 13:31 ` Jie Luo
2024-01-05 2:48 ` Sergey Ryazanov
2024-01-05 10:34 ` Jie Luo
2024-01-06 1:24 ` Sergey Ryazanov
2024-01-06 15:45 ` Andrew Lunn
2024-01-06 22:03 ` Sergey Ryazanov
2024-01-07 16:08 ` Andrew Lunn
2024-01-08 9:06 ` Jie Luo
2024-01-08 9:01 ` Jie Luo
2024-01-08 13:27 ` Andrew Lunn
2024-01-09 11:33 ` Jie Luo
2024-01-08 15:53 ` Russell King (Oracle)
2024-01-09 11:35 ` Jie Luo
2024-01-05 13:52 ` Andrew Lunn
2024-01-05 15:42 ` Alex Elder
2024-01-05 20:14 ` Sergey Ryazanov
2024-01-08 9:30 ` Jie Luo
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=20231226-twine-smolder-713cb81fa411@spud \
--to=conor@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_luoj@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®