From: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Alexandre.Bounine@idt.com, Liu Gang <Gang.Liu@freescale.com>,
Barry.Wood@idt.com, linuxppc-dev@lists.ozlabs.org,
stef.van.os@prodrive-technologies.com
Subject: Re: [PATCH] fsl-rio: add support for mapping inbound windows
Date: Tue, 12 Aug 2014 10:48:00 +0200 [thread overview]
Message-ID: <53E9D4C0.5030203@prodrive-technologies.com> (raw)
In-Reply-To: <1407274663.7427.7.camel@snotra.buserror.net>
On 08/05/2014 11:37 PM, Scott Wood wrote:
> On Tue, 2014-08-05 at 15:52 +0200, Martijn de Gouw wrote:
>> Add support for mapping and unmapping of inbound rapidio windows.
>>
>> Signed-off-by: Martijn de Gouw <martijn.de.gouw@prodrive-technologies.com>
>
> Could you elaborate in the changelog on what this fixes or makes
> possible? E.g. did the driver previously not support inbound
> transactions at all, or did it assume the window was set up by a
> bootloader?
Something like:
fsl-rio: add support for mapping inbound windows
Add support for mapping and unmapping of inbound rapidio windows.
This allows for drivers to open up a part of local memory on the
rapidio network. Also applications can use this and tranfer blocks
of data over the network.
>
> Liu Gang, could you review this?
I'll wait for the review before I post a new version.
Gr, Martijn
--
Martijn de Gouw
Engineer
Prodrive Technologies B.V.
Mobile: +31 63 17 76 161
Phone: +31 40 26 76 200
next prev parent reply other threads:[~2014-08-12 8:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 13:52 [PATCH] fsl-rio: add support for mapping inbound windows Martijn de Gouw
2014-08-05 21:37 ` Scott Wood
2014-08-12 8:48 ` Martijn de Gouw [this message]
2014-09-17 3:37 ` Gang.Liu
2014-09-03 22:42 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2014-06-13 11:09 Martijn de Gouw
2014-06-18 15:17 ` Bounine, Alexandre
2014-06-23 13:57 ` Martijn de Gouw
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=53E9D4C0.5030203@prodrive-technologies.com \
--to=martijn.de.gouw@prodrive-technologies.com \
--cc=Alexandre.Bounine@idt.com \
--cc=Barry.Wood@idt.com \
--cc=Gang.Liu@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
--cc=stef.van.os@prodrive-technologies.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 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.