From: Chunyan Zhang <zhang.lyra@gmail.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Joerg Roedel <joro@8bytes.org>, DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chunyan Zhang <chunyan.zhang@unisoc.com>,
Sheng Xu <sheng.xu@unisoc.com>,
Linux IOMMU <iommu@lists.linux-foundation.org>,
Rob Herring <robh+dt@kernel.org>,
Baolin Wang <baolin.wang7@gmail.com>,
Orson Zhai <orsonzhai@gmail.com>
Subject: Re: [PATCH 2/2] iommu: add Unisoc iommu basic driver
Date: Wed, 3 Feb 2021 09:49:43 +0800 [thread overview]
Message-ID: <CAAfSe-s9ppQBuM81KB_KWaiY5hz3cFAycFP5jd8JXysicoqFGw@mail.gmail.com> (raw)
In-Reply-To: <5e766b74-ab51-8c47-66c1-ca65bc5743cd@arm.com>
On Wed, 3 Feb 2021 at 02:02, Robin Murphy <robin.murphy@arm.com> wrote:
>
> On 2021-02-02 14:41, Joerg Roedel wrote:
> > On Tue, Feb 02, 2021 at 02:34:34PM +0000, Robin Murphy wrote:
> >> Nope, I believe if Arm Ltd. had any involvement in this I'd know about it :)
> >
> > Okay, got confused by thinking of ARM as the CPU architecture, not the
> > company :)
> > But given the intel/ and amd/ subdirectories refer to company names as
> > well, the same is true for arm/.
>
> Right, trying to group IOMMU drivers by supposed CPU architecture is
> already a demonstrable non-starter; does intel-iommu count as x86, or
> IA-64, or do you want two copies? :P
>
> I somehow doubt anyone would license one of Arm's SMMUs to go in a
> RISC-V/MIPS/etc. based SoC, but in principle, they *could*. In fact it's
> precisely cases like this one - where silicon vendors come up with their
> own little scatter-gather unit to go with their own display controller
> etc. - that I imagine are most likely to get reused if the vendor
> decides to experiment with different CPUs to reach new market segments.
Yes, I agree, I believe this iommu unit along with Unisoc's
multi-media modules can be used on other architecture SoCs, not only
ARM based.
>
> Robin.
next prev parent reply other threads:[~2021-02-03 1:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 7:32 [PATCH v2 0/2] Add Unisoc iommu basic driver Chunyan Zhang
2021-02-02 7:32 ` [PATCH v2 1/2] dt-bindings: iommu: add bindings for sprd iommu Chunyan Zhang
2021-02-02 7:32 ` [PATCH v2 2/2] iommu: add Unisoc iommu basic driver Chunyan Zhang
2021-02-02 10:42 ` [PATCH " Chunyan Zhang
2021-02-02 14:01 ` Joerg Roedel
2021-02-02 14:34 ` Robin Murphy
2021-02-02 14:41 ` Joerg Roedel
2021-02-02 18:02 ` Robin Murphy
2021-02-03 1:49 ` Chunyan Zhang [this message]
2021-02-02 14:13 ` Joerg Roedel
2021-02-03 1:45 ` Chunyan Zhang
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=CAAfSe-s9ppQBuM81KB_KWaiY5hz3cFAycFP5jd8JXysicoqFGw@mail.gmail.com \
--to=zhang.lyra@gmail.com \
--cc=baolin.wang7@gmail.com \
--cc=chunyan.zhang@unisoc.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sheng.xu@unisoc.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).