All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: robh+dt@kernel.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, stanimir.varbanov@linaro.org,
	agross@kernel.org, bjorn.andersson@linaro.org
Cc: bryan.odonoghue@linaro.org, jonathan@marek.ca, dikshita@qti.qualcomm.com
Subject: [PATCH v2 0/3] dts: qcom: sm8250: Enable venus related DT nodes
Date: Mon, 22 Feb 2021 13:28:14 +0000	[thread overview]
Message-ID: <20210222132817.1807788-1-bryan.odonoghue@linaro.org> (raw)

V2:

I noticed this series doesn't apply/build against device-tree/dt/next

- Adds dependency patch from Dmitry
- Adds "#include <dt-bindings/interconnect/qcom,sm8250.h>"

Depends on dt-binding:
https://www.spinics.net/lists/devicetree/msg406892.html

V1:
Adds
- videocc
  The clock controller for the Venus core and codec blocks

- venus
  The SoC DT description for the core, encoder, decoder + associated

The second patch is contingent on application of this pending patch
https://www.spinics.net/lists/linux-arm-msm/msg80960.html


Bryan O'Donoghue (1):
  arm64: dts: qcom: sm8250: Add venus DT node

Dmitry Baryshkov (1):
  arm64: dts: qcom: sm8250: add mmcx regulator

Jonathan Marek (1):
  arm64: dts: qcom: sm8250: Add videocc DT node

 arch/arm64/boot/dts/qcom/sm8250.dtsi | 81 ++++++++++++++++++++++++++++
 1 file changed, 81 insertions(+)

-- 
2.29.2


             reply	other threads:[~2021-02-22 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 13:28 Bryan O'Donoghue [this message]
2021-02-22 13:28 ` [PATCH v2 1/3] arm64: dts: qcom: sm8250: add mmcx regulator Bryan O'Donoghue
2021-02-22 13:28 ` [PATCH v2 2/3] arm64: dts: qcom: sm8250: Add videocc DT node Bryan O'Donoghue
2021-02-22 13:28 ` [PATCH v2 3/3] arm64: dts: qcom: sm8250: Add venus " Bryan O'Donoghue
2021-02-22 19:45   ` kernel test robot
2021-02-22 19:45     ` kernel test robot
2021-02-22 21:17   ` kernel test robot
2021-02-22 21:17     ` kernel test robot
2021-02-22 21:39   ` Dmitry Baryshkov

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=20210222132817.1807788-1-bryan.odonoghue@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dikshita@qti.qualcomm.com \
    --cc=jonathan@marek.ca \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=stanimir.varbanov@linaro.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.