From: Devi Priya <quic_devipriy@quicinc.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/3] clk: qcom: clk-rcg2: add support for rcg2 freq multi ops
Date: Mon, 27 Nov 2023 15:42:12 +0530 [thread overview]
Message-ID: <8ac05276-eec1-fb42-166a-5739822ecdd0@quicinc.com> (raw)
In-Reply-To: <655cb6e6.050a0220.35346.e9a2@mx.google.com>
On 11/21/2023 7:25 PM, Christian Marangi wrote:
>> Hi Christian,
>>
>> WARN does not get printed with the attached patchset.
>> Thanks much!
>>
> Can you also confirm that the code correctly works with your div
> scenario?
>
> Would love to have some Tested-by tag to move this further!
>
> (since it seems newer SoC after ipq807x will use this implementation
> even more)
Sorry was not available for a couple of days.
Sure, will validate and add tested-by tag.
Thanks,
Devi Priya
>
> --
next prev parent reply other threads:[~2023-11-27 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 14:00 [PATCH v6 0/3] clk: qcom: clk-rcg2: introduce support for multiple conf for same freq Christian Marangi
2023-09-16 14:00 ` [PATCH v6 1/3] clk: qcom: clk-rcg: " Christian Marangi
2023-09-16 14:00 ` [PATCH v6 2/3] clk: qcom: clk-rcg2: add support for rcg2 freq multi ops Christian Marangi
2023-11-20 10:21 ` Devi Priya
2023-11-20 18:14 ` Christian Marangi
2023-11-21 6:31 ` Devi Priya
2023-11-21 13:55 ` Christian Marangi
2023-11-27 10:12 ` Devi Priya [this message]
2023-09-16 14:00 ` [PATCH v6 3/3] clk: qcom: gcc-ipq8074: rework nss_port5/6 clock to multiple conf Christian Marangi
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=8ac05276-eec1-fb42-166a-5739822ecdd0@quicinc.com \
--to=quic_devipriy@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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®