From: Richard Acayan <mailingradian@gmail.com>
To: linux-arm-msm@vger.kernel.org
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
Richard Acayan <mailingradian@gmail.com>
Subject: [PATCH v3 0/4] SDM670 GPI DMA support
Date: Mon, 26 Sep 2022 21:48:42 -0400 [thread overview]
Message-ID: <20220927014846.32892-1-mailingradian@gmail.com> (raw)
Changes since v2:
- change fallback to sdm845 compat string (and keep compat string in
driver)
- fallback now only affects two SoCs + SDM670
Changes since v1:
- add fallback compatible
This patch series adds the compatible string for GPI DMA, needed for the
GENI interface, on Snapdragon 670.
Richard Acayan (4):
dt-bindings: dma: qcom: gpi: add fallback compatible
dt-bindings: dma: qcom: gpi: add compatible for sdm670
arm64: dts: qcom: add gpi-dma fallback compatible
dmaengine: qcom: gpi: drop redundant of_device_id entries
.../devicetree/bindings/dma/qcom,gpi.yaml | 22 ++++++++++++-------
arch/arm64/boot/dts/qcom/sm8150.dtsi | 6 ++---
arch/arm64/boot/dts/qcom/sm8250.dtsi | 6 ++---
drivers/dma/qcom/gpi.c | 2 --
4 files changed, 20 insertions(+), 16 deletions(-)
--
2.37.3
next reply other threads:[~2022-09-27 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 1:48 Richard Acayan [this message]
2022-09-27 1:48 ` [PATCH v3 1/4] dt-bindings: dma: qcom: gpi: add fallback compatible Richard Acayan
2022-09-28 7:48 ` Krzysztof Kozlowski
2022-09-27 1:48 ` [PATCH v3 2/4] dt-bindings: dma: qcom: gpi: add compatible for sdm670 Richard Acayan
2022-09-28 7:48 ` Krzysztof Kozlowski
2022-09-27 1:48 ` [PATCH v3 3/4] arm64: dts: qcom: add gpi-dma fallback compatible Richard Acayan
2022-09-28 7:48 ` Krzysztof Kozlowski
2022-09-27 1:48 ` [PATCH v3 4/4] dmaengine: qcom: gpi: drop redundant of_device_id entries Richard Acayan
2022-09-28 7:49 ` Krzysztof Kozlowski
2022-09-29 7:40 ` Vinod Koul
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=20220927014846.32892-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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 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.