devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	Krishna Reddy <vdumpa@nvidia.com>,
	Ashish Mhetre <amhetre@nvidia.com>,
	Dmitry Osipenko <dmitry.osipenko@collabora.com>,
	Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
	Janne Grunau <j@jannau.net>, Sameer Pujar <spujar@nvidia.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	devicetree@vger.kernel.org, iommu@lists.linux-foundation.org,
	linux-tegra@vger.kernel.org, asahi@lists.linux.dev
Subject: Re: [PATCH v11 0/5] iommu: Support mappings/reservations in reserved-memory regions
Date: Sat, 19 Nov 2022 10:39:08 +0100	[thread overview]
Message-ID: <Y3ikPBFYrSCWB10K@8bytes.org> (raw)
In-Reply-To: <20221111161806.630527-1-thierry.reding@gmail.com>

On Fri, Nov 11, 2022 at 05:18:01PM +0100, Thierry Reding wrote:
> Thierry Reding (5):
>   of: Introduce support for #dma-{address,size}-cells
>   of: Introduce of_translate_dma_region()
>   dt-bindings: reserved-memory: Document iommu-addresses
>   iommu: Implement of_iommu_get_resv_regions()
>   iommu: dma: Use of_iommu_get_resv_regions()
> 
>  .../reserved-memory/reserved-memory.yaml      | 73 ++++++++++++++
>  drivers/iommu/dma-iommu.c                     |  3 +
>  drivers/iommu/of_iommu.c                      | 94 +++++++++++++++++++
>  drivers/of/address.c                          | 84 +++++++++++++----
>  drivers/of/base.c                             | 70 +++++++++++---
>  drivers/of/of_private.h                       | 14 ++-
>  include/linux/of.h                            | 17 +++-
>  include/linux/of_address.h                    |  4 +-
>  include/linux/of_iommu.h                      |  8 ++
>  9 files changed, 329 insertions(+), 38 deletions(-)

Despite this lacking some essential reviews, what is the plan with this
code? Should it go through the IOMMU or DT tree?

Regards,

	Joerg

      parent reply	other threads:[~2022-11-19  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 16:18 [PATCH v11 0/5] iommu: Support mappings/reservations in reserved-memory regions Thierry Reding
2022-11-11 16:18 ` [PATCH v11 1/5] of: Introduce support for #dma-{address,size}-cells Thierry Reding
2022-11-11 16:18 ` [PATCH v11 2/5] of: Introduce of_translate_dma_region() Thierry Reding
2022-11-11 16:18 ` [PATCH v11 3/5] dt-bindings: reserved-memory: Document iommu-addresses Thierry Reding
2022-11-11 16:18 ` [PATCH v11 4/5] iommu: Implement of_iommu_get_resv_regions() Thierry Reding
2022-11-11 16:18 ` [PATCH v11 5/5] iommu: dma: Use of_iommu_get_resv_regions() Thierry Reding
2022-11-19  9:39 ` Joerg Roedel [this message]

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=Y3ikPBFYrSCWB10K@8bytes.org \
    --to=joro@8bytes.org \
    --cc=alyssa.rosenzweig@collabora.com \
    --cc=amhetre@nvidia.com \
    --cc=asahi@lists.linux.dev \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.osipenko@collabora.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=j@jannau.net \
    --cc=l.stach@pengutronix.de \
    --cc=linux-tegra@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=spujar@nvidia.com \
    --cc=thierry.reding@gmail.com \
    --cc=vdumpa@nvidia.com \
    --cc=will@kernel.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 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).