public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Melody Olvera <quic_molvera@quicinc.com>,
	Andy Gross <agross@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Taniya Das <quic_tdas@quicinc.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] clk: qcom: Add QDU1000 and QRU1000 GCC support
Date: Wed, 18 Jan 2023 20:44:02 -0600	[thread overview]
Message-ID: <20230119024402.yfiekwp6grl3kn6q@builder.lan> (raw)
In-Reply-To: <8ecb84b5-93a5-691d-4a7d-5daed0e432e4@linaro.org>

On Thu, Jan 12, 2023 at 11:15:57PM +0200, Dmitry Baryshkov wrote:
> On 12/01/2023 22:44, Melody Olvera wrote:
> > From: Taniya Das <quic_tdas@quicinc.com>
> > 
> > Add Global Clock Controller (GCC) support for QDU1000 and QRU1000 SoCs.
> > 
> > Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
> > Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
> > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > ---
> >   drivers/clk/qcom/Kconfig       |    8 +
> >   drivers/clk/qcom/Makefile      |    1 +
> >   drivers/clk/qcom/gcc-qdu1000.c | 2653 ++++++++++++++++++++++++++++++++
> >   3 files changed, 2662 insertions(+)
> >   create mode 100644 drivers/clk/qcom/gcc-qdu1000.c
> > 
> 
> [skipped the rest]
> 
> > +};
> > +
> > +static struct clk_regmap_mux gcc_pcie_0_pipe_clk_src = {
> > +	.reg = 0x9d064,
> > +	.shift = 0,
> > +	.width = 2,
> > +	.parent_map = gcc_parent_map_7,
> > +	.clkr = {
> > +		.hw.init = &(const struct clk_init_data) {
> > +			.name = "gcc_pcie_0_pipe_clk_src",
> > +			.parent_data = gcc_parent_data_7,
> > +			.num_parents = ARRAY_SIZE(gcc_parent_data_7),
> > +			.ops = &clk_regmap_mux_closest_ops,
> 
> I think this should use clk_regmap_phy_mux_ops.
> 

I believe so too. So I updated this as I applied the patch.

@Melody, please send a fix if bringing up PCIe shows this to be wrong.

Thanks,
Bjorn

> > +		},
> > +	},
> > +};
> > +--
> With best wishes
> Dmitry
> 

  reply	other threads:[~2023-01-19  2:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 20:44 [PATCH v6 0/2] clk: qcom: Add clocks for the QDU1000 and QRU1000 SoCs Melody Olvera
2023-01-12 20:44 ` [PATCH v6 1/2] dt-bindings: clock: Add QDU1000 and QRU1000 GCC clocks Melody Olvera
2023-01-13  8:43   ` Krzysztof Kozlowski
2023-01-12 20:44 ` [PATCH v6 2/2] clk: qcom: Add QDU1000 and QRU1000 GCC support Melody Olvera
2023-01-12 21:15   ` Dmitry Baryshkov
2023-01-19  2:44     ` Bjorn Andersson [this message]
2023-01-19  2:42 ` [PATCH v6 0/2] clk: qcom: Add clocks for the QDU1000 and QRU1000 SoCs 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=20230119024402.yfiekwp6grl3kn6q@builder.lan \
    --to=andersson@kernel.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@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=quic_molvera@quicinc.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robh+dt@kernel.org \
    --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