All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Prasad Malisetty (Temp) (QUIC)" <quic_pmaliset@quicinc.com>
To: "dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
	"Prasad Malisetty (Temp) (QUIC)" <quic_pmaliset@quicinc.com>,
	"Andy Gross" <agross@kernel.org>,
	"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
	"Stephen Boyd" <swboyd@chromium.org>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Taniya Das" <tdas@codeaurora.org>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>
Cc: "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: RE: [PATCH v1 0/5] PCI: qcom: rework pipe_clk/pipe_clk_src handling
Date: Mon, 4 Apr 2022 05:03:54 +0000	[thread overview]
Message-ID: <CO1PR02MB853744542779C0C2CD61C1E4E9E59@CO1PR02MB8537.namprd02.prod.outlook.com> (raw)
In-Reply-To: <edfff61f-02a0-7962-a72c-97ef5f14ba76@linaro.org>

Hi Dmitry,

Please find inline comments below.

Thanks
-Prasad

> -----Original Message-----
> From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Sent: Wednesday, March 30, 2022 6:26 PM
> To: Prasad Malisetty (Temp) (QUIC) <quic_pmaliset@quicinc.com>; Andy Gross
> <agross@kernel.org>; bjorn.andersson@linaro.org; Stephen Boyd
> <swboyd@chromium.org>; Michael Turquette <mturquette@baylibre.com>;
> Taniya Das <tdas@codeaurora.org>; Lorenzo Pieralisi
> <lorenzo.pieralisi@arm.com>; Krzysztof Wilczyński <kw@linux.com>; Bjorn
> Helgaas <bhelgaas@google.com>
> Cc: linux-arm-msm@vger.kernel.org; linux-clk@vger.kernel.org; linux-
> pci@vger.kernel.org
> Subject: Re: [PATCH v1 0/5] PCI: qcom: rework pipe_clk/pipe_clk_src handling
> 
> On 23/03/2022 11:50, Dmitry Baryshkov wrote:
> > PCIe pipe clk (and some other clocks) must be parked to the "safe"
> > source (bi_tcxo) when corresponding GDSC is turned off and on again.
> > Currently this is handcoded in the PCIe driver by reparenting the
> > gcc_pipe_N_clk_src clock.
> >
> > Instead of doing it manually, follow the approach used by
> > clk_rcg2_shared_ops and implement this parking in the enable() and
> > disable() clock operations for respective pipe clocks.
> 
> Prasad, can we please get your comments on this patchset?
> Since you have submitted original patchset for sc7280, it looks like you should be
> interested in testing that this patchset doesn't break your devices.
> 
Thanks for optimizing pipe clock handling. 
Sure Dmitry, the validation is in progress ( Need to validate power consumption and other stuff).
I will update once done.

Thanks,
-Prasad.
> >
> > Changes since RFC:
> >   - Rework clk-regmap-mux fields. Specify safe parent as P_* value rather
> >     than specifying the register value directly
> >   - Expand commit message to the first patch to specially mention that
> >     it is required only on newer generations of Qualcomm chipsets.
> >
> > Dmitry Baryshkov (5):
> >    clk: qcom: regmap-mux: add pipe clk implementation
> >    clk: qcom: gcc-sm8450: use new clk_regmap_mux_safe_ops for PCIe pipe
> >      clocks
> >    clk: qcom: gcc-sc7280: use new clk_regmap_mux_safe_ops for PCIe pipe
> >      clocks
> >    PCI: qcom: Remove unnecessary pipe_clk handling
> >    PCI: qcom: Drop manual pipe_clk_src handling
> >
> >   drivers/clk/qcom/clk-regmap-mux.c      | 78 +++++++++++++++++++++++
> >   drivers/clk/qcom/clk-regmap-mux.h      |  3 +
> >   drivers/clk/qcom/gcc-sc7280.c          |  6 +-
> >   drivers/clk/qcom/gcc-sm8450.c          |  6 +-
> >   drivers/pci/controller/dwc/pcie-qcom.c | 87 +-------------------------
> >   5 files changed, 92 insertions(+), 88 deletions(-)
> >
> 
> 
> --
> With best wishes
> Dmitry

      reply	other threads:[~2022-04-04  5:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23  8:50 [PATCH v1 0/5] PCI: qcom: rework pipe_clk/pipe_clk_src handling Dmitry Baryshkov
2022-03-23  8:50 ` [PATCH v1 1/5] clk: qcom: regmap-mux: add pipe clk implementation Dmitry Baryshkov
2022-04-08 11:15   ` Lorenzo Pieralisi
2022-04-12 18:45     ` Bjorn Andersson
2022-04-13  8:16       ` Johan Hovold
2022-04-13  9:56       ` Lorenzo Pieralisi
2022-04-12 18:32   ` Bjorn Andersson
2022-03-23  8:50 ` [PATCH v1 2/5] clk: qcom: gcc-sm8450: use new clk_regmap_mux_safe_ops for PCIe pipe clocks Dmitry Baryshkov
2022-03-23  8:50 ` [PATCH v1 3/5] clk: qcom: gcc-sc7280: " Dmitry Baryshkov
2022-03-23  8:50 ` [PATCH v1 4/5] PCI: qcom: Remove unnecessary pipe_clk handling Dmitry Baryshkov
2022-04-01 10:17   ` Johan Hovold
2022-03-23  8:50 ` [PATCH v1 5/5] PCI: qcom: Drop manual pipe_clk_src handling Dmitry Baryshkov
2022-03-30 12:56 ` [PATCH v1 0/5] PCI: qcom: rework pipe_clk/pipe_clk_src handling Dmitry Baryshkov
2022-04-04  5:03   ` Prasad Malisetty (Temp) (QUIC) [this message]

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=CO1PR02MB853744542779C0C2CD61C1E4E9E59@CO1PR02MB8537.namprd02.prod.outlook.com \
    --to=quic_pmaliset@quicinc.com \
    --cc=agross@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=kw@linux.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=swboyd@chromium.org \
    --cc=tdas@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.