Messages in this thread |  | | Date | Sun, 9 May 2021 19:28:43 +0530 | From | Vinod Koul <> | Subject | Re: [PATCH v2 14/17] dma: qcom: bam_dma: Create a new header file for BAM DMA driver |
| |
On 06-05-21, 03:07, Bhupesh Sharma wrote: > Create a new header file for BAM DMA driver to make sure > that it can be included in the follow-up patch to defer probing > drivers which require BAM DMA driver to be first probed successfully. > > Cc: Thara Gopinath <thara.gopinath@linaro.org> > Cc: Bjorn Andersson <bjorn.andersson@linaro.org> > Cc: Rob Herring <robh+dt@kernel.org> > Cc: Andy Gross <agross@kernel.org> > Cc: Herbert Xu <herbert@gondor.apana.org.au> > Cc: David S. Miller <davem@davemloft.net> > Cc: Stephen Boyd <sboyd@kernel.org> > Cc: Michael Turquette <mturquette@baylibre.com> > Cc: Vinod Koul <vkoul@kernel.org> > Cc: dmaengine@vger.kernel.org > Cc: linux-clk@vger.kernel.org > Cc: linux-crypto@vger.kernel.org > Cc: devicetree@vger.kernel.org > Cc: linux-kernel@vger.kernel.org > Cc: bhupesh.linux@gmail.com > Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org> > --- > drivers/dma/qcom/bam_dma.c | 283 +----------------------------------- > include/soc/qcom/bam_dma.h | 290 +++++++++++++++++++++++++++++++++++++
1. Please use -M with move patches...
2. susbsytem is dmaengine
3. Why move..? These things are internal to the driver and I dont think it is wise for clients to use everything here... If the client needs to know defer probe, it should request a channel and check the status returned for EPROBE_DEFER
Thanks
-- ~Vinod
|  |