From: Thierry Reding <thierry.reding@gmail.com>
To: Will Deacon <will@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jon Hunter <jonathanh@nvidia.com>,
Nicolin Chen <nicolinc@nvidia.com>,
Krishna Reddy <vdumpa@nvidia.com>,
linux-tegra@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
Dmitry Osipenko <digetx@gmail.com>
Subject: Re: [GIT PULL] memory: Tegra memory controller for v5.14
Date: Tue, 8 Jun 2021 16:38:48 +0200 [thread overview]
Message-ID: <YL+A+MPjjaa3nSwq@orome.fritz.box> (raw)
In-Reply-To: <20210608120128.GB10174@willie-the-truck>
[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]
On Tue, Jun 08, 2021 at 01:01:29PM +0100, Will Deacon wrote:
> Hi Krzysztof, Thierry,
>
> On Mon, Jun 07, 2021 at 10:49:10AM +0200, Krzysztof Kozlowski wrote:
> > Hi Thierry and Will,
> >
> > This is the pull for you to base further SMMU aptches (prevent early SMMU
> > faults).
>
> This is a tonne of code for me to pull into the SMMU tree given that I only
> want one patch!
>
> Thierry, if I just stick:
>
> https://lore.kernel.org/r/20210603164632.1000458-4-thierry.reding@gmail.com
>
> on its own branch, can you stitch together whatever you need?
I'm not sure I understand what you're proposing. For reference, here's
the set of patches that I sent out:
1. memory: tegra: Implement SID override programming
2. dt-bindings: arm-smmu: Add Tegra186 compatible string
3. iommu/arm-smmu: Implement ->probe_finalize()
4. iommu/arm-smmu: tegra: Detect number of instances at runtime
5. iommu/arm-smmu: tegra: Implement SID override programming
6. iommu/arm-smmu: Use Tegra implementation on Tegra186
7. arm64: tegra: Use correct compatible string for Tegra186 SMMU
8. arm64: tegra: Hook up memory controller to SMMU on Tegra186
9. arm64: tegra: Enable SMMU support on Tegra194
Krzysztof already picked up patch 1 and I was assuming that you'd pick
up 2-6 because they are to the ARM SMMU driver. However, if you're
primarily interested in just patch 3, which is more "core" ARM SMMU than
the rest, which are Tegra-specific, then I suppose what we could do is
for you to give an Acked-by on the rest (2, 4-6) and then Krzysztof or I
can pick them up and take them via ARM SoC, based on the stable branch
from your tree that only has patch 3.
Patch 6 touches arm-smmu-impl.c, though it's a two-line change that
touches only the Tegra-specific matching bit in arm_smmu_impl_init(), so
the likelihood of that conflicting with anything else is fairly small.
Is that what you were proposing?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-08 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 8:49 [GIT PULL] memory: Tegra memory controller for v5.14 Krzysztof Kozlowski
[not found] ` <20210608120128.GB10174@willie-the-truck>
2021-06-08 14:38 ` Thierry Reding [this message]
[not found] ` <20210608164851.GB10994@willie-the-truck>
2021-06-10 9:19 ` Thierry Reding
2021-06-10 14:23 ` Krzysztof Kozlowski
2021-06-10 15:05 ` Thierry Reding
[not found] ` <20210610172958.GA14188@willie-the-truck>
2021-06-11 6:43 ` Krzysztof Kozlowski
2021-06-09 13:20 ` Krzysztof Kozlowski
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=YL+A+MPjjaa3nSwq@orome.fritz.box \
--to=thierry.reding@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=digetx@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=olof@lixom.net \
--cc=robin.murphy@arm.com \
--cc=soc@kernel.org \
--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