public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Acayan <mailingradian@gmail.com>
To: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Georgi Djakov <djakov@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: Odelu Kukatla <quic_okukatla@quicinc.com>,
	Luca Weiss <luca@z3ntu.xyz>,
	Richard Acayan <mailingradian@gmail.com>
Subject: Re: [PATCH v4 0/4] SDM670 Interconnects
Date: Tue, 10 Jan 2023 19:57:19 -0500	[thread overview]
Message-ID: <Y74Jb3PXt49NR93K@radian> (raw)
In-Reply-To: <20230111005155.50452-1-mailingradian@gmail.com>

On Tue, Jan 10, 2023 at 07:51:51PM -0500, Richard Acayan wrote:
> Changes since v3:
>  - fix a merge conflict on linux-next (1/4)
This conflict is caused by fae28c82bbbd ("dt-bindings: interconnect:
split SC8280XP to own schema"), so it now depends on:

https://lore.kernel.org/r/20221223132040.80858-2-krzysztof.kozlowski@linaro.org

> 
> Changes since v2:
>  - change qcom,sdm670.h to qcom,sdm670-rpmh.h (2/4)
>  - use SPDX v3 license identifiers (1/4, 2/4)
>  - accumulate ack tag (1/4)
>  - format changelog (0/4)
> 
> Changes since v1:
>  - change qcom,sdm670.h to qcom,sdm670-rpmh.h (1/4, 4/4)
> 
> This series adds interconnects and consumers to the Snapdragon 670.
> 
> Richard Acayan (4):
>   dt-bindings: interconnect: add sdm670 interconnects
>   interconnect: qcom: add sdm670 interconnects
>   arm64: dts: qcom: sdm670: add interconnects
>   arm64: dts: qcom: sdm670: add opps for peripherals
> 
>  .../bindings/interconnect/qcom,rpmh.yaml      |   8 +
>  arch/arm64/boot/dts/qcom/sdm670.dtsi          | 165 +++++++
>  drivers/interconnect/qcom/Kconfig             |   9 +
>  drivers/interconnect/qcom/Makefile            |   2 +
>  drivers/interconnect/qcom/sdm670.c            | 440 ++++++++++++++++++
>  drivers/interconnect/qcom/sdm670.h            | 128 +++++
>  .../interconnect/qcom,sdm670-rpmh.h           | 136 ++++++
>  7 files changed, 888 insertions(+)
>  create mode 100644 drivers/interconnect/qcom/sdm670.c
>  create mode 100644 drivers/interconnect/qcom/sdm670.h
>  create mode 100644 include/dt-bindings/interconnect/qcom,sdm670-rpmh.h
> 
> -- 
> 2.39.0
> 

      parent reply	other threads:[~2023-01-11  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  0:51 [PATCH v4 0/4] SDM670 Interconnects Richard Acayan
2023-01-11  0:51 ` [PATCH v4 1/4] dt-bindings: interconnect: add sdm670 interconnects Richard Acayan
2023-01-11  0:51 ` [PATCH v4 2/4] interconnect: qcom: " Richard Acayan
2023-01-11  0:51 ` [PATCH v4 3/4] arm64: dts: qcom: sdm670: add interconnects Richard Acayan
2023-01-11  0:51 ` [PATCH v4 4/4] arm64: dts: qcom: sdm670: add opps for peripherals Richard Acayan
2023-01-11  0:57 ` Richard Acayan [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=Y74Jb3PXt49NR93K@radian \
    --to=mailingradian@gmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=luca@z3ntu.xyz \
    --cc=quic_okukatla@quicinc.com \
    --cc=robh+dt@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