From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.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: Fri, 16 Nov 2012 14:37:55 +0200 [thread overview]
Message-ID: <1353069475.11158.356.camel@smile> (raw)
In-Reply-To: <CAKohpokuGtgz6ohBPR9m0rnu0vhsyi7ywBvfWkSGSps5=PnYEA@mail.gmail.com>
On Fri, 2012-11-16 at 09:59 +0530, Viresh Kumar wrote:
> On 15 November 2012 23:28, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > On Thu, Nov 15, 2012 at 5:38 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> >> On 15 November 2012 20:57, Andy Shevchenko
> >> <andriy.shevchenko@linux.intel.com> wrote:
> >>> 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.
> >>
> >> What i meant to say was, set_runtime_config() must have already done this part.
> >
> > On one hand it is true. On the other - *_prep* functions use
> > explicitly passed parameter. I doubt there is a consistency between
> > value in slave config passed via dwc_control and value passed as
> > explicit function parameter.
>
> I believe it should be consistent.
>
> @Vinod: Why have we duplicated direction? Once in prep_* and then in
> slave_config?
Documentation and TODO list say that slave_config.direction is kinda
deprecated.
>
> --
> viresh
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2012-11-16 12:38 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
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 [this message]
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=1353069475.11158.356.camel@smile \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.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