From: Vinod Koul <vkoul@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Mark Brown <broonie@kernel.org>, Wolfram Sang <wsa@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>, Andy Gross <agross@kernel.org>,
Sumit Semwal <sumit.semwal@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>,
linux-spi@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/5] Add and enable GPI DMA users
Date: Fri, 25 Jun 2021 10:52:08 +0530 [thread overview]
Message-ID: <20210625052213.32260-1-vkoul@kernel.org> (raw)
Hello,
This series adds the GPI DMA in qcom geni spi and i2c drivers.
For this we first need to move GENI_IF_DISABLE_RO to common
headers and then add support for gpi dma in geni drivers.
Also, to reuse the dma-mapping in spi, we add a new field dma_map_dev to
allow controllers to pass a specific device for dma-mapping
Then, we add spi and i2c geni driver changes to support this DMA.
Changes since v2:
- Add core spi patch for dma_map_dev addition
- rework the logic for getting and releasing channels in both driver, also
ensure proper cleanup
- Fix the comments recieved from Doug and Bjorn
- Add kernel-doc changes for enum geni_se_xfer_mode
Changes since v1:
- add r-b from Bjorn on patch 1
- add more details in log for patch 2
- Fix the comments from Doug and Bjorn for patch3, notable use read, modify
update for irq registers, use geni_se_irq_clear() for irq, dont update
single bit registers, add a bit more description for gpi dma etc
Vinod Koul (5):
soc: qcom: geni: move GENI_IF_DISABLE_RO to common header
soc: qcom: geni: Add support for gpi dma
spi: core: add dma_map_dev for dma device
spi: spi-geni-qcom: Add support for GPI dma
i2c: qcom-geni: Add support for GPI DMA
drivers/i2c/busses/i2c-qcom-geni.c | 309 ++++++++++++++++++++++++++-
drivers/soc/qcom/qcom-geni-se.c | 30 ++-
drivers/spi/spi-geni-qcom.c | 329 +++++++++++++++++++++++++++--
drivers/spi/spi.c | 4 +
include/linux/qcom-geni-se.h | 19 +-
include/linux/spi/spi.h | 1 +
6 files changed, 667 insertions(+), 25 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-25 5:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 5:22 Vinod Koul [this message]
2021-06-25 5:22 ` [PATCH v3 1/5] soc: qcom: geni: move GENI_IF_DISABLE_RO to common header Vinod Koul
2021-06-28 23:37 ` Doug Anderson
2021-06-25 5:22 ` [PATCH v3 2/5] soc: qcom: geni: Add support for gpi dma Vinod Koul
2021-06-28 23:38 ` Doug Anderson
2021-06-29 3:37 ` Vinod Koul
2021-06-25 5:22 ` [PATCH v3 3/5] spi: core: add dma_map_dev for dma device Vinod Koul
2021-06-25 5:22 ` [PATCH v3 4/5] spi: spi-geni-qcom: Add support for GPI dma Vinod Koul
2021-06-25 12:10 ` kernel test robot
2021-06-28 23:37 ` Doug Anderson
2021-10-14 16:04 ` Vinod Koul
2021-10-14 16:55 ` Doug Anderson
2021-10-18 16:53 ` Vinod Koul
2021-06-25 5:22 ` [PATCH v3 5/5] i2c: qcom-geni: Add support for GPI DMA Vinod Koul
2021-06-25 13:24 ` (subset) [PATCH v3 0/5] Add and enable GPI DMA users Mark Brown
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=20210625052213.32260-1-vkoul@kernel.org \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mka@chromium.org \
--cc=sumit.semwal@linaro.org \
--cc=wsa@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).