From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
Viresh Kumar <viresh.linux@gmail.com>,
linux-kernel@vger.kernel.org,
spear-devel <spear-devel@list.st.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
"Svahn, Kai" <kai.svahn@intel.com>
Subject: Re: [PATCH] dw_dmac: adjust slave_id accordingly to request line base
Date: Tue, 19 Feb 2013 23:17:24 +0100 [thread overview]
Message-ID: <5123F9F4.70409@intel.com> (raw)
In-Reply-To: <1361264544.28241.52.camel@smile>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8"; format="flowed", Size: 1491 bytes --]
On 2/19/2013 10:02 AM, Andy Shevchenko wrote:
> On Mon, 2013-01-28 at 13:04 +0200, Andy Shevchenko wrote:
>> On some hardware configurations we have got the request line with the offset.
>> The patch introduces convert_slave_id() helper for that cases. The request line
>> base is got from the platform device resources provided by the IORESOURCE_DMA
>> type.
> Hi, Vinod.
>
> v3.8 is just out, and we have not got any proposal from anyone how to
> make our approach better. So, I'm just wondering about current state.
>
> Rafael, could you share your opinion about our case with CSRT and
> request line base (perhaps you need to go through the entire thread)?
>
Well, I can do that, but Mika is the author of the patches, so he should
know. :-)
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk
Sad Rejonowy Gdansk Polnoc w Gdansku,
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego,
numer KRS 101882
NIP 957-07-52-316
Kapital zakladowy 200.000 zl
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2013-02-19 22:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 11:04 [PATCH] dw_dmac: adjust slave_id accordingly to request line base Andy Shevchenko
2013-01-29 4:59 ` Viresh Kumar
2013-01-29 5:22 ` Mika Westerberg
2013-01-29 15:27 ` Viresh Kumar
2013-01-30 7:32 ` Andy Shevchenko
2013-01-30 8:01 ` Viresh Kumar
2013-01-30 8:07 ` Andy Shevchenko
2013-02-07 13:22 ` Shevchenko, Andriy
2013-02-12 15:56 ` Vinod Koul
2013-02-12 16:34 ` Andy Shevchenko
2013-02-12 15:53 ` Vinod Koul
2013-02-12 16:43 ` Mika Westerberg
2013-02-12 17:34 ` Vinod Koul
2013-02-12 19:02 ` Mika Westerberg
2013-02-14 9:57 ` Vinod Koul
2013-02-14 10:17 ` Mika Westerberg
2013-02-07 13:28 ` Viresh Kumar
2013-02-19 9:02 ` Andy Shevchenko
2013-02-19 22:17 ` Rafael J. Wysocki [this message]
2013-02-20 6:04 ` Vinod Koul
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=5123F9F4.70409@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=kai.svahn@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=spear-devel@list.st.com \
--cc=vinod.koul@intel.com \
--cc=viresh.linux@gmail.com \
/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).