From: Vinod Koul <vkoul@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: Enable Qualcomm GPI DMA Driver
Date: Thu, 24 Feb 2022 09:57:08 +0530 [thread overview]
Message-ID: <YhcJHGsdY/XQPOt8@matsya> (raw)
In-Reply-To: <Yhb7Q91cEdgayc6c@builder.lan>
On 23-02-22, 21:28, Bjorn Andersson wrote:
> On Mon 21 Feb 22:24 CST 2022, Vinod Koul wrote:
>
> > Qualcomm GPI DMA Driver is used for DMA transfers for Serial engines
> > like Geni I2C and SPI.
> >
> > Enable this dma driver
> >
>
> Can you please include a motivation in the commit message why this has
> to be builtin?
Sure, traditionally DMAengine drivers are always initialized early on (typically most
of the drivers are arch init level) so that it is available to users
early on as well..
Current config has many dmaengine drivers as inbuilt...
Will add more details and send
>
> Thanks,
> Bjorn
>
> > Signed-off-by: Vinod Koul <vkoul@kernel.org>
> > ---
> > arch/arm64/configs/defconfig | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> > index 30516dc0b70e..d73913f082d7 100644
> > --- a/arch/arm64/configs/defconfig
> > +++ b/arch/arm64/configs/defconfig
> > @@ -948,6 +948,7 @@ CONFIG_PL330_DMA=y
> > CONFIG_TEGRA20_APB_DMA=y
> > CONFIG_TEGRA210_ADMA=m
> > CONFIG_QCOM_BAM_DMA=y
> > +CONFIG_QCOM_GPI_DMA=y
> > CONFIG_QCOM_HIDMA_MGMT=y
> > CONFIG_QCOM_HIDMA=y
> > CONFIG_RCAR_DMAC=y
> > --
> > 2.34.1
> >
--
~Vinod
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-02-24 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 4:24 [PATCH] arm64: defconfig: Enable Qualcomm GPI DMA Driver Vinod Koul
2022-02-24 3:28 ` Bjorn Andersson
2022-02-24 4:27 ` Vinod Koul [this message]
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=YhcJHGsdY/XQPOt8@matsya \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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).