From: Hiroshi Doyu <hdoyu@nvidia.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "kmpark@infradead.org" <kmpark@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Krishna Reddy <vdumpa@nvidia.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: Linux 3.4-rc1
Date: Tue, 3 Apr 2012 08:29:54 +0200 [thread overview]
Message-ID: <20120403.092954.1292069011296905405.hdoyu@nvidia.com> (raw)
In-Reply-To: <CA+55aFw1ZG9R2MzgXmi0YE64t+xH95QnVuJB55sQ6xgDbnzkyQ@mail.gmail.com>
From: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 3.4-rc1
Date: Tue, 3 Apr 2012 05:57:26 +0200
Message-ID:
<CA+55aFw1ZG9R2MzgXmi0YE64t+xH95QnVuJB55sQ6xgDbnzkyQ@mail.gmail.com>
> On Mon, Apr 2, 2012 at 7:57 PM, Kyungmin Park <kmpark@infradead.org> wrote:
> > On Sun, Apr 1, 2012 at 8:58 AM, Linus Torvalds
> >>
> >> - DMA-mapping framework. The tree now has a few more acks from
> >> people, and it's largely in the same situation as HSI is: I'll
> >> probably pull, but I really wanted the users who are impacted to
> >> actually talk to me about it.
> >
> > Now Marek and Nvidia persons are used it for DMA mapping based IOMMU.
> >
> > Are there other person who help to merge it?
> > (+CC related persons).
>
> I want the people who want it to contact me and talk about what they
> do with it. So far, I haven't seen anything.
Nvidia ARM SoC Tegra3 has IOMMU(SMMU), and most of its peripheral
devices can be clients of IOMMU. Their IOMMU'abiblity can be
configured. With DMA-mapping API, we wouldn't have to change any of
device driver code with\without IOMMU, but those 'dma_addr_t' could be
physical address or device virtual address trasparently.
next prev parent reply other threads:[~2012-04-03 6:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 23:58 Linux 3.4-rc1 Linus Torvalds
2012-04-01 0:09 ` Christoph Hellwig
2012-04-01 1:46 ` Shea Levy
2012-04-01 3:11 ` Linus Torvalds
2012-04-01 1:48 ` Shea Levy
2012-04-01 2:07 ` Shea Levy
2012-04-01 8:34 ` Ingo Molnar
2012-04-01 12:03 ` Stephen Rothwell
2012-04-01 19:19 ` David Miller
2012-04-01 13:14 ` linux-next stats (Was: Linux 3.4-rc1) Stephen Rothwell
2012-04-01 15:34 ` Linux 3.4-rc1 Rob Clark
2012-04-02 3:40 ` Kyungmin Park
2012-04-02 8:41 ` Daniel Vetter
2012-04-04 12:24 ` Subash Patel
2012-04-04 12:33 ` Anca Emanuel
2012-04-05 7:41 ` Marek Szyprowski
2012-04-02 12:31 ` Alex Deucher
2012-04-02 9:15 ` Artem Bityutskiy
2012-04-02 9:20 ` Shubhrajyoti Datta
2012-04-02 15:48 ` Linus Walleij
2012-04-02 20:30 ` Carlos Chinea
2012-04-03 2:57 ` Kyungmin Park
2012-04-03 3:57 ` Linus Torvalds
2012-04-03 6:29 ` Hiroshi Doyu [this message]
2012-04-03 9:07 ` Arnd Bergmann
2012-04-03 14:58 ` Jerome Glisse
2012-04-03 15:35 ` Arnd Bergmann
2012-04-03 19:26 ` Krishna Reddy
2012-04-04 12:10 ` Anca Emanuel
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=20120403.092954.1292069011296905405.hdoyu@nvidia.com \
--to=hdoyu@nvidia.com \
--cc=arnd@arndb.de \
--cc=kmpark@infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vdumpa@nvidia.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).