Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Marko Mäkelä" <marko.makela@iki.fi>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	linux-arm-msm@vger.kernel.org,
	Christian Marangi <ansuelsmth@gmail.com>,
	Robert Marko <robimarko@gmail.com>
Subject: Re: [PATCH] clk: qcom: gcc-ipq6018: rework nss_port5 clock to multiple conf
Date: Mon, 4 Aug 2025 17:09:02 +0300	[thread overview]
Message-ID: <aJC-_jzdwP-1NnlD@jyty> (raw)
In-Reply-To: <61b1ac3d-8481-4731-b24d-2864e24625b4@oss.qualcomm.com>

Sat, Aug 02, 2025 at 01:51:31PM +0200, Konrad Dybcio wrote:
>On 8/2/25 11:55 AM, Marko Mäkelä wrote:
>> Rework nss_port5 to use the new multiple configuration implementation
>> and correctly fix the clocks for this port under some corner case.
>>
>> In OpenWrt, this patch avoids intermittent dmesg errors of the form
>> nss_port5_rx_clk_src: rcg didn't update its configuration.
>>
>> This is a mechanical, straightforward port of
>> commit e88f03230dc07aa3293b6aeb078bd27370bb2594
>> ("clk: qcom: gcc-ipq8074: rework nss_port5/6 clock to multiple conf")
>> to gcc-ipq6018, with two conflicts resolved: different frequency of the
>> P_XO clock source, and only 5 Ethernet ports.
>>
>> This was originally developed by JiaY-shi <shi05275@163.com>.
>
>Hmm.. I'm not sure what to think about this, given that person seems
>not to be using their full name (or maybe it is the full name, I don't
>know) and hasn't provided a sign-off, but on the other hand this isn't
>a very inventive change, so I don't *really* mind - up to you, Bjorn

This basically is the result of executing the following and resolving 
the rather trivial conflicts:

git show e88f03230dc07aa3293b6aeb078bd27370bb2594|
patch drivers/clk/qcom/gcc-ipq6018.c

I actually did that and compared the result to the original patch.

I believe that my Signed-off-by is valid and sufficient due to 
Developer's Certificate of Origin 1.1 (b), "The contribution is based 
upon previous work."  That "previous work" would be the gcc-ipq8074 fix 
that this is a subset of.  This is what I tried to convey in my commit 
message.  In the name of openness, I wanted to credit the person who 
provided the patch to the OpenWrt community; see 
<https://github.com/openwrt/openwrt/pull/14950> and 
<https://forum.openwrt.org/t//232618/4>.

I did play with the thought of modifying the patch a little so that I 
could without hesitation submit it as my own work.  Namely, I could have 
replaced two ".num_parents = 7" with equivalent ARRAY_SIZE expressions, 
similar to gcc-ipq8074.c.  However, that would have violated the 
"Separate your changes" guideline.

>FWIW for the patch contents:
>
>Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Thank you!

	Marko

  reply	other threads:[~2025-08-04 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-02  9:55 [PATCH] clk: qcom: gcc-ipq6018: rework nss_port5 clock to multiple conf Marko Mäkelä
2025-08-02 11:51 ` Konrad Dybcio
2025-08-04 14:09   ` Marko Mäkelä [this message]
2025-08-11 18:41 ` Bjorn Andersson

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=aJC-_jzdwP-1NnlD@jyty \
    --to=marko.makela@iki.fi \
    --cc=andersson@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robimarko@gmail.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