From: Jonathan McDowell <noodles@earth.li>
To: Vinod Koul <vkoul@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Dan Williams <dan.j.williams@intel.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Thomas Pedersen <twp@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
dmaengine@vger.kernel.org
Subject: Re: [PATCH] dmaengine: qcom: Add ADM driver
Date: Fri, 18 Sep 2020 19:39:19 +0100 [thread overview]
Message-ID: <20200918183919.GQ3411@earth.li> (raw)
In-Reply-To: <20200918113443.GN2968@vkoul-mobl>
On Fri, Sep 18, 2020 at 05:04:43PM +0530, Vinod Koul wrote:
> Hello Jonathan
>
> On 16-09-20, 07:43, Jonathan McDowell wrote:
> > From: Andy Gross <agross@codeaurora.org>
> >
> > (I'm not sure how best to attribute this. It's originally from Andy
> > Gross, the version I picked up was a later version from Thomas Pedersen,
> > and I can't find clear indication of why the latest version wasn't
> > applied. The device tree details were added back in September 2014. The
> > driver is the missing piece in mainline for IPQ8064 NAND support and
> > I've been using it successfully with my RB3011 device on 5.8+)
>
> Yeah not sure why the driver was missed :(
> Btw this note is helpful but not great for log, you should add it after
> sob lines.
Noted, I'll move it for v2.
> > diff --git a/drivers/dma/qcom/Kconfig b/drivers/dma/qcom/Kconfig
> > index 3bcb689162c6..75ee112ccea9 100644
> > --- a/drivers/dma/qcom/Kconfig
> > +++ b/drivers/dma/qcom/Kconfig
> > @@ -28,3 +28,13 @@ config QCOM_HIDMA
> > (user to kernel, kernel to kernel, etc.). It only supports
> > memcpy interface. The core is not intended for general
> > purpose slave DMA.
> > +
> > +config QCOM_ADM
>
> alphabetical sort please
Ok.
> > + tristate "Qualcomm ADM support"
> > + depends on ARCH_QCOM || (COMPILE_TEST && OF && ARM)
>
> Why COMPILE_TEST && OF? just COMPILE_TEST should be fine
Turns out (ARCH_QCOM || COMPILE_TEST) && !64BIT is sufficient.
> > + select DMA_ENGINE
> > + select DMA_VIRTUAL_CHANNELS
> > + ---help---
> > + Enable support for the Qualcomm ADM DMA controller. This controller
> > + provides DMA capabilities for both general purpose and on-chip
> > + peripheral devices.
> > diff --git a/drivers/dma/qcom/Makefile b/drivers/dma/qcom/Makefile
> > index 1ae92da88b0c..98a021fc6fe5 100644
> > --- a/drivers/dma/qcom/Makefile
> > +++ b/drivers/dma/qcom/Makefile
> > @@ -4,3 +4,4 @@ obj-$(CONFIG_QCOM_HIDMA_MGMT) += hdma_mgmt.o
> > hdma_mgmt-objs := hidma_mgmt.o hidma_mgmt_sys.o
> > obj-$(CONFIG_QCOM_HIDMA) += hdma.o
> > hdma-objs := hidma_ll.o hidma.o hidma_dbg.o
> > +obj-$(CONFIG_QCOM_ADM) += qcom_adm.o
>
> alphabetical sort please
Ok.
> > +/* channel conf */
> > +#define ADM_CH_CONF_SHADOW_EN BIT(12)
> > +#define ADM_CH_CONF_MPU_DISABLE BIT(11)
> > +#define ADM_CH_CONF_PERM_MPU_CONF BIT(9)
> > +#define ADM_CH_CONF_FORCE_RSLT_EN BIT(7)
> > +#define ADM_CH_CONF_SEC_DOMAIN(ee) (((ee & 0x3) << 4) | ((ee & 0x4) << 11))
>
> USE FIELD_PREP for this?
I can't see a way to neatly use FIELD_PREP for a split field; am I
missing something?
(other pieces fixed up for v2 as well; I'd run checkpatch but not with
--strict. Will post once I've actually tested it.)
J.
--
Minorities are the foundation of | .''`. Debian GNU/Linux Developer
society. | : :' : Happy to accept PGP signed
| `. `' or encrypted mail - RSA
| `- key on the keyservers.
next prev parent reply other threads:[~2020-09-18 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 6:43 [PATCH] dmaengine: qcom: Add ADM driver Jonathan McDowell
2020-09-18 11:34 ` Vinod Koul
2020-09-18 18:39 ` Jonathan McDowell [this message]
2020-09-19 18:57 ` [PATCH v2] " Jonathan McDowell
2020-09-20 18:12 ` [PATCH v3] " Jonathan McDowell
2020-09-21 8:41 ` Philipp Zabel
2020-09-23 19:40 ` [PATCH v4] " Jonathan McDowell
2020-10-25 18:11 ` Jonathan McDowell
2020-10-28 16:04 ` Vinod Koul
2020-11-09 11:41 ` Vinod Koul
2020-11-09 19:04 ` Jonathan McDowell
2020-11-10 4:54 ` Vinod Koul
2020-11-14 14:02 ` [PATCH v5] " Jonathan McDowell
2020-11-18 15:50 ` 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=20200918183919.GQ3411@earth.li \
--to=noodles@earth.li \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=twp@codeaurora.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).