From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Kiran Kumar C.S.K" <quic_kkumarcs@quicinc.com>,
Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Russell King <linux@armlinux.org.uk>,
Jacob Keller <jacob.e.keller@intel.com>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, vsmuthu@qti.qualcomm.com,
arastogi@qti.qualcomm.com, linchen@qti.qualcomm.com,
john@phrozen.org, Luo Jie <quic_luoj@quicinc.com>,
Pavithra R <quic_pavir@quicinc.com>,
"Suruchi Agarwal (QUIC)" <quic_suruchia@quicinc.com>,
"Lei Wei (QUIC)" <quic_leiwei@quicinc.com>
Subject: Re: RFC: Advice on adding support for Qualcomm IPQ9574 SoC Ethernet
Date: Fri, 4 Oct 2024 16:03:11 +0200 [thread overview]
Message-ID: <664a3cc0-8274-43f8-88e7-fff7b650205d@linaro.org> (raw)
In-Reply-To: <6c0118b9-f883-4fb5-9e69-a9095869d37f@quicinc.com>
On 04/10/2024 15:06, Kiran Kumar C.S.K wrote:
>>> The MII Rx/Tx clocks are supplied from the NSS clock controller to the
>>> PCS's MII channels. To represent this in the DTS, the PCS node in the
>>> DTS is configured with the MII Rx/Tx clock that it consumes, using
>>> macros for clocks which are exported from the NSS CC driver in a header
>>> file. So, there will be a compile-time dependency for the dtbindings/DTS
>>> on the NSS CC patch series. We will clearly call out this dependency in
>>> the cover letter of the PCS driver. Hope that this approach is ok.
>>
>> Since there is a compile time dependency, you might want to ask for
>> the clock patches to be put into a stable branch which can be merged
>> into netdev.
>>
>
> Sure. We will request for such a stable branch merge once the NSS CC
> patches are accepted by the reviewers. Could the 'net' tree be one such
> stable branch option to merge the NSS CC driver?
NAK.
This is not needed and cannot happen.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-04 14:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f0f0c065-bf7c-4106-b5e2-bfafc6b52101@quicinc.com>
2024-10-02 20:37 ` RFC: Advice on adding support for Qualcomm IPQ9574 SoC Ethernet Kiran Kumar C.S.K
2024-10-02 21:28 ` Andrew Lunn
2024-10-03 17:50 ` Kiran Kumar C.S.K
2024-10-03 18:42 ` Andrew Lunn
2024-10-04 13:06 ` Kiran Kumar C.S.K
2024-10-04 13:31 ` Andrew Lunn
2024-10-04 14:03 ` Krzysztof Kozlowski [this message]
2024-10-04 14:02 ` Krzysztof Kozlowski
2024-10-03 19:20 ` Bjorn Andersson
2024-10-04 14:17 ` Kiran Kumar C.S.K
2024-10-04 14:50 ` Andrew Lunn
2024-10-08 19:31 ` Kiran Kumar C.S.K
2024-10-05 18:30 ` Bjorn Andersson
2024-10-08 19:33 ` Kiran Kumar C.S.K
2024-10-04 14:24 ` Russell King (Oracle)
2024-10-22 9:59 ` Kiran Kumar C.S.K
2024-10-22 13:37 ` Andrew Lunn
2024-10-24 13:25 ` Kiran Kumar C.S.K
2024-10-24 14:27 ` Andrew Lunn
2024-10-25 13:03 ` Kiran Kumar C.S.K
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=664a3cc0-8274-43f8-88e7-fff7b650205d@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=arastogi@qti.qualcomm.com \
--cc=bhupesh.sharma@linaro.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jacob.e.keller@intel.com \
--cc=john@phrozen.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linchen@qti.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=quic_kkumarcs@quicinc.com \
--cc=quic_leiwei@quicinc.com \
--cc=quic_luoj@quicinc.com \
--cc=quic_pavir@quicinc.com \
--cc=quic_suruchia@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=vsmuthu@qti.qualcomm.com \
/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;
as well as URLs for NNTP newsgroup(s).