From: Nicolin Chen <nicoleotsuka@gmail.com>
To: thierry.reding@gmail.com, joro@8bytes.org, digetx@gmail.com
Cc: vdumpa@nvidia.com, jonathanh@nvidia.com,
linux-tegra@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/3] iommu/tegra-smmu: Add PCI support
Date: Fri, 2 Oct 2020 23:59:44 -0700 [thread overview]
Message-ID: <20201003065947.18671-1-nicoleotsuka@gmail.com> (raw)
This series is to add PCI support in tegra-smmu driver.
Changelog (Detail in each patch)
v4->v5
* PATCH-1 Cleaned two variables inits
* PATCH-2 Fixed put() in ->of_xlate() and Updated commit message
* PATCH-3 Added Dmitry's Reviewed-by
v3->v4
* Dropped helper function
* Found another way to get smmu pointer
v2->v3
* Replaced with devm_tegra_get_memory_controller
* Updated changes by following Dmitry's comments
v1->v2
* Added PATCH-1 suggested by Dmitry
* Reworked PATCH-2 to unify certain code
Nicolin Chen (3):
iommu/tegra-smmu: Use fwspec in tegra_smmu_(de)attach_dev
iommu/tegra-smmu: Rework tegra_smmu_probe_device()
iommu/tegra-smmu: Add PCI support
drivers/iommu/tegra-smmu.c | 183 ++++++++++++-------------------------
1 file changed, 59 insertions(+), 124 deletions(-)
--
2.17.1
next reply other threads:[~2020-10-03 7:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 6:59 Nicolin Chen [this message]
2020-10-03 6:59 ` [PATCH v5 1/3] iommu/tegra-smmu: Use fwspec in tegra_smmu_(de)attach_dev Nicolin Chen
2020-10-03 14:14 ` Dmitry Osipenko
2020-10-03 6:59 ` [PATCH v5 2/3] iommu/tegra-smmu: Rework tegra_smmu_probe_device() Nicolin Chen
2020-10-03 14:05 ` Dmitry Osipenko
2020-10-04 22:04 ` Nicolin Chen
2020-10-03 14:06 ` Dmitry Osipenko
2020-10-04 21:57 ` Nicolin Chen
2020-10-05 8:41 ` Dmitry Osipenko
2020-10-05 10:56 ` Thierry Reding
2020-10-06 1:14 ` Nicolin Chen
2020-10-03 14:19 ` Dmitry Osipenko
2020-10-03 6:59 ` [PATCH v5 3/3] iommu/tegra-smmu: Add PCI support Nicolin Chen
2020-10-03 14:16 ` Dmitry Osipenko
2020-10-04 22:08 ` Nicolin Chen
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=20201003065947.18671-1-nicoleotsuka@gmail.com \
--to=nicoleotsuka@gmail.com \
--cc=digetx@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--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