devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Imran Shaik <quic_imrashai@quicinc.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: Melody Olvera <quic_molvera@quicinc.com>,
	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,
	Jagadeesh Kona <quic_jkona@quicinc.com>,
	Satya Priya Kakitapalli <quic_skakitap@quicinc.com>,
	Ajit Pandey <quic_ajipan@quicinc.com>
Subject: Re: [PATCH 0/2] Update GCC clocks for QDU1000 and QRU1000 SoCs
Date: Fri, 16 Jun 2023 13:21:52 +0200	[thread overview]
Message-ID: <c963cc67-5c8d-4503-af0e-082ee0be8688@linaro.org> (raw)
In-Reply-To: <20230616104941.921555-1-quic_imrashai@quicinc.com>

On 16.06.2023 12:49, Imran Shaik wrote:
> Update GCC clocks and add support for GDSCs for QDU1000 and QRU1000 SoCs.
> Also, add support for v2 variant as well.
Does that imply the first submission concerned v1/pre-mass-production chips?

We usually don't support these upstream, as they are rather short-lived and
never (officially, anyway) escape Qualcomm internal..

Konrad
> 
> Imran Shaik (2):
>   dt-bindings: clock: Update GCC clocks for QDU1000 and QRU1000 SoCs
>   clk: qcom: gcc-qdu1000: Update GCC clocks and add support for GDSCs
> 
>  .../bindings/clock/qcom,qdu1000-gcc.yaml      |   6 +-
>  drivers/clk/qcom/gcc-qdu1000.c                | 162 ++++++++++++------
>  include/dt-bindings/clock/qcom,qdu1000-gcc.h  |   4 +-
>  3 files changed, 118 insertions(+), 54 deletions(-)
> 

  parent reply	other threads:[~2023-06-16 11:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 10:49 [PATCH 0/2] Update GCC clocks for QDU1000 and QRU1000 SoCs Imran Shaik
2023-06-16 10:49 ` [PATCH 1/2] dt-bindings: clock: " Imran Shaik
2023-06-16 11:33   ` Krzysztof Kozlowski
2023-06-22 13:45     ` Krzysztof Kozlowski
2023-06-23 10:07       ` Imran Shaik
2023-06-16 10:49 ` [PATCH 2/2] clk: qcom: gcc-qdu1000: Update GCC clocks and add support for GDSCs Imran Shaik
2023-06-16 11:20   ` Dmitry Baryshkov
2023-06-23 10:08     ` Imran Shaik
2023-06-23 14:06       ` Dmitry Baryshkov
2023-06-16 11:22   ` Konrad Dybcio
2023-06-23 10:12     ` Imran Shaik
2023-06-16 11:21 ` Konrad Dybcio [this message]
2023-06-23 10:07   ` [PATCH 0/2] Update GCC clocks for QDU1000 and QRU1000 SoCs Imran Shaik

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=c963cc67-5c8d-4503-af0e-082ee0be8688@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.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_ajipan@quicinc.com \
    --cc=quic_imrashai@quicinc.com \
    --cc=quic_jkona@quicinc.com \
    --cc=quic_molvera@quicinc.com \
    --cc=quic_skakitap@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;
as well as URLs for NNTP newsgroup(s).