public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 2/2] dw_dmac: make usage of dw_dma_slave optional
Date: Thu, 15 Nov 2012 17:27:49 +0200	[thread overview]
Message-ID: <1352993269.11158.340.camel@smile> (raw)
In-Reply-To: <CAKohpo=F1SmD0qCn9ybOOQ9VXWFQ-BY=udPgrWYPa23M2PuU_g@mail.gmail.com>

On Thu, 2012-11-15 at 20:54 +0530, Viresh Kumar wrote: 
> On 15 November 2012 20:51, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Thu, 2012-11-15 at 20:28 +0530, viresh kumar wrote:
> >> On Thu, Nov 15, 2012 at 7:50 PM, Andy Shevchenko
> >> <andriy.shevchenko@linux.intel.com> wrote:
> >> > diff --git a/drivers/dma/dw_dmac.c b/drivers/dma/dw_dmac.c
> >>
> >> > +static inline bool dwc_is_slave(struct dma_slave_config *sconfig)
> >> > +{
> >> > +       return is_slave_direction(sconfig->direction);
> >> > +}
> >>
> >> I will not buy this one. Why hide the real implementation, call
> >> is_slave_direction()
> >> directly.
> >
> > There is no strong reason to keep it so.
> >
> >> > @@ -1344,6 +1352,8 @@ struct dw_cyclic_desc *dw_dma_cyclic_prep(struct dma_chan *chan,
> >> > +       sconfig->direction = direction;
> >> > +
> >>
> >> > @@ -1718,6 +1728,7 @@ static int __devinit dw_probe(struct platform_device *pdev)
> >> > +               dwc->dma_sconfig.direction = DMA_TRANS_NONE;
> >>
> >> Why do you need above changes??
> >
> > This one is not needed indeed. But we have to look after default (0)
> > enum value.
> 
> I am asking about all lines where you are doing sconfig->direction = foo;

Well, the prep_* should assign the value due to changes of check in the
dwc_descriptor_complete. Otherwise we will potentially skip some
important piece of code.


-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2012-11-15 15:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 14:20 [PATCH 1/2] dw_dmac: check direction properly in dw_dma_cyclic_prep Andy Shevchenko
2012-11-15 14:20 ` [PATCH 2/2] dw_dmac: make usage of dw_dma_slave optional Andy Shevchenko
2012-11-15 14:58   ` viresh kumar
2012-11-15 15:21     ` Andy Shevchenko
2012-11-15 15:24       ` Viresh Kumar
2012-11-15 15:27         ` Andy Shevchenko [this message]
2012-11-15 15:38           ` Viresh Kumar
2012-11-15 17:58             ` Andy Shevchenko
2012-11-16  4:29               ` Viresh Kumar
2012-11-16 12:37                 ` Andy Shevchenko
2012-11-15 14:35 ` [PATCH 1/2] dw_dmac: check direction properly in dw_dma_cyclic_prep viresh kumar
2012-11-15 14:58   ` viresh kumar
2012-11-15 15:17     ` Andy Shevchenko
2012-11-16 12:37   ` Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
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

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=1352993269.11158.340.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox