From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
spear-devel <spear-devel@list.st.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dw_dmac: store direction in the custom channel structure
Date: Tue, 20 Nov 2012 17:10:32 +0200 [thread overview]
Message-ID: <1353424232.20110.18.camel@smile> (raw)
In-Reply-To: <CAKohpom4Dd=ubVL8shGSOvCCUBYqRRPOViS6V0_7SrOzADb95A@mail.gmail.com>
On Tue, 2012-11-20 at 19:38 +0530, Viresh Kumar wrote:
> On 20 November 2012 19:08, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > Currently the direction value is come from the generic slave configuration
>
> s/is come/comes
>
> > structure and explicitly as a preparation function parameter. The first one is
> > kinda obsoleted. Thus, we have to store the value passed to the preparation
> > function somewhere in our structures to be able to use it later. The best
> > candidate to provide the storage is a custom channel structure. Until now we
> > still keep and check the direction field of the slave config structure as well.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > drivers/dma/dw_dmac.c | 10 ++++++++--
> > drivers/dma/dw_dmac_regs.h | 2 ++
> > 2 files changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/dma/dw_dmac.c b/drivers/dma/dw_dmac.c
> > index 5e2c4dc..58c6d3c 100644
> > --- a/drivers/dma/dw_dmac.c
> > +++ b/drivers/dma/dw_dmac.c
> > @@ -178,9 +178,9 @@ static void dwc_initialize(struct dw_dma_chan *dwc)
> > cfghi = dws->cfg_hi;
> > cfglo |= dws->cfg_lo & ~DWC_CFGL_CH_PRIOR_MASK;
> > } else {
> > - if (dwc->dma_sconfig.direction == DMA_MEM_TO_DEV)
> > + if (dwc->direction == DMA_MEM_TO_DEV)
> > cfghi = DWC_CFGH_DST_PER(dwc->dma_sconfig.slave_id);
> > - else if (dwc->dma_sconfig.direction == DMA_DEV_TO_MEM)
> > + else if (dwc->direction == DMA_DEV_TO_MEM)
> > cfghi = DWC_CFGH_SRC_PER(dwc->dma_sconfig.slave_id);
> > }
>
> I have a doubt here. This routine is called both for memcpy and slave transfers.
> Earlier if (dws), code was used to check slave/non-slave transfer but with your
> earlier patch, for if (!dws) case too, there can be slave transfers
> based on direction.
>
> Consider a situation. A channel is used for slave transfers and have
> direction set
> to DMA_DEV_TO_MEM. Now, channel is freed and used for memcpy. Now the
> direction value is retained as we haven't updated it. So, is this a
> potential bug?
Yeah, good point. I think we have to set direction in all possible entry
points (prep functions only?). It means at least we need to update
memcpy prep as well.
I'll update patch tomorrow.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2012-11-20 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 13:38 [PATCH 1/2] dw_dmac: store direction in the custom channel structure Andy Shevchenko
2012-11-20 13:38 ` [PATCH 2/2] dw_dmac: make usage of dw_dma_slave optional Andy Shevchenko
2012-11-20 14:10 ` Viresh Kumar
2012-11-20 14:08 ` [PATCH 1/2] dw_dmac: store direction in the custom channel structure Viresh Kumar
2012-11-20 15:10 ` Andy Shevchenko [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=1353424232.20110.18.camel@smile \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spear-devel@list.st.com \
--cc=vinod.koul@intel.com \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.