From: Rajesh Patil <rajpat@codeaurora.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Mark Brown <broonie@kernel.org>,
Doug Anderson <dianders@chromium.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, rnayak@codeaurora.org,
saiprakash.ranjan@codeaurora.org, msavaliy@qti.qualcomm.com,
skakit@codeaurora.org, sboyd@kernel.org, mka@chromium.org,
Rajesh Patil <rajpat@codeaurora.org>
Subject: [PATCH V1 0/2] Add device tree compatible for sc7180 SoC
Date: Thu, 30 Sep 2021 15:54:08 +0530 [thread overview]
Message-ID: <1632997450-32293-1-git-send-email-rajpat@codeaurora.org> (raw)
- As per Doug's comments
1. Added device tree compatible in dt-bindings
2. Added "qcom,sc718-qspi" in qspi node
Rajesh Patil (2):
dt-bindings: spi: Add sc7180 support
arm64: dts: qcom: sc7180: Add qspi compatible
Documentation/devicetree/bindings/spi/qcom,spi-qcom-qspi.yaml | 1 +
arch/arm64/boot/dts/qcom/sc7180.dtsi | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2021-09-30 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 10:24 Rajesh Patil [this message]
2021-09-30 10:24 ` [PATCH V1 1/2] dt-bindings: spi: Add sc7180 support Rajesh Patil
2021-09-30 13:35 ` Doug Anderson
2021-10-01 20:25 ` Mark Brown
2021-09-30 10:24 ` [PATCH V1 2/2] arm64: dts: qcom: sc7180: Add qspi compatible Rajesh Patil
2021-09-30 13:35 ` Doug Anderson
2021-10-02 1:37 ` (subset) [PATCH V1 0/2] Add device tree compatible for sc7180 SoC Mark Brown
2021-10-17 15:31 ` Bjorn Andersson
2021-09-30 10:30 Rajesh Patil
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=1632997450-32293-1-git-send-email-rajpat@codeaurora.org \
--to=rajpat@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=msavaliy@qti.qualcomm.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=skakit@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.