From: Thierry Reding <thierry.reding@gmail.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH v2 1/4] dt-bindings: arm-smmu: Document nvidia,memory-controller property
Date: Tue, 8 Mar 2022 16:59:05 +0100 [thread overview]
Message-ID: <Yid9SWbpPQQhNgA4@orome> (raw)
In-Reply-To: <Ygz7QD4EJX3vZJtD@orome>
[-- Attachment #1.1: Type: text/plain, Size: 1331 bytes --]
On Wed, Feb 16, 2022 at 02:25:20PM +0100, Thierry Reding wrote:
> On Thu, Dec 09, 2021 at 05:35:57PM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > On NVIDIA SoC's the ARM SMMU needs to interact with the memory
> > controller in order to map memory clients to the corresponding stream
> > IDs. Document how the nvidia,memory-controller property can be used to
> > achieve this.
> >
> > Note that this is a backwards-incompatible change that is, however,
> > necessary to ensure correctness. Without the new property, most of the
> > devices would still work but it is not guaranteed that all will.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > Changes in v2:
> > - clarify why the new nvidia,memory-controller property is required
> >
> > .../devicetree/bindings/iommu/arm,smmu.yaml | 17 +++++++++++++++++
> > 1 file changed, 17 insertions(+)
>
> Hi Joerg,
>
> can you pick up patches 1-3 of this series? DT bindings have been
> reviewed by Rob and Will acked the ARM SMMU change. I can take the
> device tree changes (patch 4) through the Tegra tree.
Will, Robin, Joerg,
I haven't seen this show up in linux-next yet but was hoping to see this
go in for v5.18. Anything I can do to help this move along?
Thanks,
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: arm-smmu: Document nvidia,memory-controller property
Date: Tue, 8 Mar 2022 16:59:05 +0100 [thread overview]
Message-ID: <Yid9SWbpPQQhNgA4@orome> (raw)
In-Reply-To: <Ygz7QD4EJX3vZJtD@orome>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
On Wed, Feb 16, 2022 at 02:25:20PM +0100, Thierry Reding wrote:
> On Thu, Dec 09, 2021 at 05:35:57PM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > On NVIDIA SoC's the ARM SMMU needs to interact with the memory
> > controller in order to map memory clients to the corresponding stream
> > IDs. Document how the nvidia,memory-controller property can be used to
> > achieve this.
> >
> > Note that this is a backwards-incompatible change that is, however,
> > necessary to ensure correctness. Without the new property, most of the
> > devices would still work but it is not guaranteed that all will.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > Changes in v2:
> > - clarify why the new nvidia,memory-controller property is required
> >
> > .../devicetree/bindings/iommu/arm,smmu.yaml | 17 +++++++++++++++++
> > 1 file changed, 17 insertions(+)
>
> Hi Joerg,
>
> can you pick up patches 1-3 of this series? DT bindings have been
> reviewed by Rob and Will acked the ARM SMMU change. I can take the
> device tree changes (patch 4) through the Tegra tree.
Will, Robin, Joerg,
I haven't seen this show up in linux-next yet but was hoping to see this
go in for v5.18. Anything I can do to help this move along?
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh+dt@kernel.org>
Cc: Jon Hunter <jonathanh@nvidia.com>,
iommu@lists.linux-foundation.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: arm-smmu: Document nvidia,memory-controller property
Date: Tue, 8 Mar 2022 16:59:05 +0100 [thread overview]
Message-ID: <Yid9SWbpPQQhNgA4@orome> (raw)
In-Reply-To: <Ygz7QD4EJX3vZJtD@orome>
[-- Attachment #1.1: Type: text/plain, Size: 1331 bytes --]
On Wed, Feb 16, 2022 at 02:25:20PM +0100, Thierry Reding wrote:
> On Thu, Dec 09, 2021 at 05:35:57PM +0100, Thierry Reding wrote:
> > From: Thierry Reding <treding@nvidia.com>
> >
> > On NVIDIA SoC's the ARM SMMU needs to interact with the memory
> > controller in order to map memory clients to the corresponding stream
> > IDs. Document how the nvidia,memory-controller property can be used to
> > achieve this.
> >
> > Note that this is a backwards-incompatible change that is, however,
> > necessary to ensure correctness. Without the new property, most of the
> > devices would still work but it is not guaranteed that all will.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > Changes in v2:
> > - clarify why the new nvidia,memory-controller property is required
> >
> > .../devicetree/bindings/iommu/arm,smmu.yaml | 17 +++++++++++++++++
> > 1 file changed, 17 insertions(+)
>
> Hi Joerg,
>
> can you pick up patches 1-3 of this series? DT bindings have been
> reviewed by Rob and Will acked the ARM SMMU change. I can take the
> device tree changes (patch 4) through the Tegra tree.
Will, Robin, Joerg,
I haven't seen this show up in linux-next yet but was hoping to see this
go in for v5.18. Anything I can do to help this move along?
Thanks,
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-08 15:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 16:35 [PATCH v2 1/4] dt-bindings: arm-smmu: Document nvidia, memory-controller property Thierry Reding
2021-12-09 16:35 ` Thierry Reding
2021-12-09 16:35 ` [PATCH v2 1/4] dt-bindings: arm-smmu: Document nvidia,memory-controller property Thierry Reding
2021-12-09 16:35 ` [PATCH v2 2/4] dt-bindings: arm-smmu: Add compatible for Tegra234 SOC Thierry Reding
2021-12-09 16:35 ` Thierry Reding
2021-12-09 16:35 ` Thierry Reding
2021-12-09 16:35 ` [PATCH v2 3/4] iommu/arm-smmu: Support Tegra234 SMMU Thierry Reding
2021-12-09 16:35 ` Thierry Reding
2021-12-09 16:35 ` Thierry Reding
2021-12-13 18:18 ` Will Deacon
2021-12-13 18:18 ` Will Deacon
2021-12-13 18:18 ` Will Deacon
2021-12-09 16:36 ` [PATCH v2 4/4] arm64: tegra: Add Tegra234 IOMMUs Thierry Reding
2021-12-09 16:36 ` Thierry Reding
2021-12-09 16:36 ` Thierry Reding
2021-12-15 19:16 ` [PATCH v2 1/4] dt-bindings: arm-smmu: Document nvidia,memory-controller property Rob Herring
2021-12-15 19:16 ` Rob Herring
2021-12-15 19:16 ` Rob Herring
2022-02-16 13:25 ` Thierry Reding
2022-02-16 13:25 ` Thierry Reding
2022-02-16 13:25 ` Thierry Reding
2022-03-08 15:59 ` Thierry Reding [this message]
2022-03-08 15:59 ` Thierry Reding
2022-03-08 15:59 ` Thierry Reding
2022-03-09 12:43 ` Will Deacon
2022-03-09 12:43 ` Will Deacon
2022-03-09 12:43 ` Will Deacon
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=Yid9SWbpPQQhNgA4@orome \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.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 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.