From: Mitchel Humpherys <mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Varun Sethi <Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
will.deacon-5wv7dgnIgG8@public.gmane.org
Subject: Re: [RFC][PATCH 2/2] Add support of the IOMMU_DEVICE flag.
Date: Mon, 06 Oct 2014 16:32:34 -0700 [thread overview]
Message-ID: <vnkwr3ykn59p.fsf@mitchelh-linux.qualcomm.com> (raw)
In-Reply-To: <1412591296-31934-2-git-send-email-Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org> (Varun Sethi's message of "Mon, 6 Oct 2014 15:58:16 +0530")
On Mon, Oct 06 2014 at 03:28:16 AM, Varun Sethi <Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org> wrote:
> This flag is used for specifying access to device memory. SMMU would apply
> device memory attributes for a DMA transaction. This is required for setting
> access to GIC registers, for generating message interrupts. This would ensure that
Nit: long line and trailing whitespace.
-Mitch
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-10-06 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 10:28 [RFC][PATCH 1/2] Introduce the IOMMU_DEVICE flag Varun Sethi
[not found] ` <1412591296-31934-1-git-send-email-Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-10-06 10:28 ` [RFC][PATCH 2/2] Add support of " Varun Sethi
[not found] ` <1412591296-31934-2-git-send-email-Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2014-10-06 11:17 ` Will Deacon
[not found] ` <20141006111716.GF12935-5wv7dgnIgG8@public.gmane.org>
2014-10-06 11:34 ` Varun Sethi
2014-10-06 23:32 ` Mitchel Humpherys [this message]
2014-10-06 11:04 ` [RFC][PATCH 1/2] Introduce " Will Deacon
[not found] ` <20141006110428.GE12935-5wv7dgnIgG8@public.gmane.org>
2014-10-06 11:51 ` Varun Sethi
2014-10-06 18:35 ` Olav Haugan
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=vnkwr3ykn59p.fsf@mitchelh-linux.qualcomm.com \
--to=mitchelh-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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.