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 v5 0/3] SDM670 GPI DMA support
Date: Fri, 7 Oct 2022 17:36:37 -0400 [thread overview]
Message-ID: <20221007213640.85469-1-mailingradian@gmail.com> (raw)
Changes since v4:
- drop dts patch (to be sent separately)
- accumulate review tags
Changes since v3:
- keep other compatible strings in driver and add comment
- accumulate review tags
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 (3):
dt-bindings: dma: qcom: gpi: add fallback compatible
dt-bindings: dma: qcom: gpi: add compatible for sdm670
dmaengine: qcom: deprecate redundant of_device_id entries
.../devicetree/bindings/dma/qcom,gpi.yaml | 22 ++++++++++++-------
drivers/dma/qcom/gpi.c | 4 ++++
2 files changed, 18 insertions(+), 8 deletions(-)
--
2.38.0
next reply other threads:[~2022-10-07 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 21:36 Richard Acayan [this message]
2022-10-07 21:36 ` [PATCH v5 1/3] dt-bindings: dma: qcom: gpi: add fallback compatible Richard Acayan
2022-10-17 21:37 ` Krzysztof Kozlowski
2022-10-07 21:36 ` [PATCH v5 2/3] dt-bindings: dma: qcom: gpi: add compatible for sdm670 Richard Acayan
2022-10-07 21:36 ` [PATCH v5 3/3] dmaengine: qcom: deprecate redundant of_device_id entries Richard Acayan
2022-10-17 21:06 ` [PATCH v5 0/3] SDM670 GPI DMA support Richard Acayan
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=20221007213640.85469-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 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).