From: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
To: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: Nicolas Chauvet <kwizart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH v2 0/4] iommu: A couple of urgent fixes
Date: Fri, 6 Feb 2015 12:04:40 -0600 [thread overview]
Message-ID: <54D50238.1010709@ti.com> (raw)
In-Reply-To: <1423219448-22683-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Thierry,
On 02/06/2015 04:44 AM, Thierry Reding wrote:
> From: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Hi Joerg,
>
> Here are a couple of urgent fixes for a regression on old Tegra devices
> related to IOMMU support. The issue is that many drivers think it's a
> good idea to register IOMMU support unconditionally, which is not the
> smart thing to do at all on multi-platform kernels. This probably went
> unnoticed for a while because the offending drivers aren't enabled in
> any of the multi-platform default configurations. Fedora ARM has their
> own config where the offending drivers did get enabled, hence caused a
> regression on Tegra20. I would expect the same regression to exist on a
> number of other SoCs, possibly all that support IOMMU.
>
> I've tried to keep the patches minimal in the hopes of still getting
> this into v3.19-rc8 or the final release to avoid the regression.
>
> Changes in v2:
> - avoid potential leak by dropping references to device tree nodes
> - remove fixups from module exit functions since they are unused
Thanks for the revised patches, tested them on the OMAP platforms. I was
not able to apply the iommu/msm patch though against 3.19-rc7 cleanly.
regards
Suman
> Thierry
>
> Thierry Reding (4):
> iommu/exynos: Play nice in multi-platform builds
> iommu/omap: Play nice in multi-platform builds
> iommu/rockchip: Play nice in multi-platform builds
> iommu/msm: Mark driver BROKEN
>
> drivers/iommu/Kconfig | 1 +
> drivers/iommu/exynos-iommu.c | 7 +++++++
> drivers/iommu/omap-iommu.c | 7 +++++++
> drivers/iommu/rockchip-iommu.c | 7 +++++++
> 4 files changed, 22 insertions(+)
>
next prev parent reply other threads:[~2015-02-06 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 10:44 [PATCH v2 0/4] iommu: A couple of urgent fixes Thierry Reding
[not found] ` <1423219448-22683-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-06 10:44 ` [PATCH v2 1/4] iommu/exynos: Play nice in multi-platform builds Thierry Reding
2015-02-06 10:44 ` [PATCH v2 2/4] iommu/omap: " Thierry Reding
[not found] ` <1423219448-22683-3-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-09 9:31 ` Laurent Pinchart
2015-02-06 10:44 ` [PATCH v2 3/4] iommu/rockchip: " Thierry Reding
2015-02-06 10:44 ` [PATCH v2 4/4] iommu/msm: Mark driver BROKEN Thierry Reding
2015-02-06 18:04 ` Suman Anna [this message]
2015-02-25 12:43 ` [PATCH v2 0/4] iommu: A couple of urgent fixes Joerg Roedel
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=54D50238.1010709@ti.com \
--to=s-anna-l0cymroini0@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=kwizart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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