From: Marcel Ziswiler <marcel.ziswiler-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
To: "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"contact-W9ppeneeCTY@public.gmane.org"
<contact-W9ppeneeCTY@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org"
<jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org"
<mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org"
<treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org"
<swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: Register host1x node with iommu binding on tegra124
Date: Tue, 11 Jul 2017 14:54:04 +0000 [thread overview]
Message-ID: <1499784841.1520.20.camel@toradex.com> (raw)
In-Reply-To: <1499763009.1340.11.camel-W9ppeneeCTY@public.gmane.org>
On Tue, 2017-07-11 at 11:50 +0300, Paul Kocialkowski wrote:
> On Sun, 2017-07-09 at 19:36 +0300, Paul Kocialkowski wrote:
> > This registers the host1x node with the SMMU (as HC swgroup) to
> > allow
> > the host1x code to attach to it. It avoid failing the probe
> > sequence,
> > which resulted in the tegra drm driver not probing and thus nothing
> > being displayed on-screen.
>
> Fixes: 404bfb78daf3 ("gpu: host1x: Add IOMMU support")
>
> > Signed-off-by: Paul Kocialkowski <contact-
> > W9ppeneeCTY@public.gmane.org>
Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Tested-on: Apalis TK1, Jetson-TK1
> > ---
> > arch/arm/boot/dts/tegra124.dtsi | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/boot/dts/tegra124.dtsi
> > b/arch/arm/boot/dts/tegra124.dtsi
> > index 187a36c6d0fc..b3b89befffeb 100644
> > --- a/arch/arm/boot/dts/tegra124.dtsi
> > +++ b/arch/arm/boot/dts/tegra124.dtsi
> > @@ -85,6 +85,7 @@
> > clocks = <&tegra_car TEGRA124_CLK_HOST1X>;
> > resets = <&tegra_car 28>;
> > reset-names = "host1x";
> > + iommus = <&mc TEGRA_SWGROUP_HC>;
> >
> > #address-cells = <2>;
> > #size-cells = <2>;
So I take it we still will need this one moving forward, correct?
How about tegra30, I guess the same applies there, isn't it? Should I
send a patch or are you guys doing that?
WARNING: multiple messages have this Message-ID (diff)
From: marcel.ziswiler@toradex.com (Marcel Ziswiler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: Register host1x node with iommu binding on tegra124
Date: Tue, 11 Jul 2017 14:54:04 +0000 [thread overview]
Message-ID: <1499784841.1520.20.camel@toradex.com> (raw)
In-Reply-To: <1499763009.1340.11.camel@paulk.fr>
On Tue, 2017-07-11 at 11:50 +0300, Paul Kocialkowski wrote:
> On Sun, 2017-07-09 at 19:36 +0300, Paul Kocialkowski wrote:
> > This registers the host1x node with the SMMU (as HC swgroup) to
> > allow
> > the host1x code to attach to it. It avoid failing the probe
> > sequence,
> > which resulted in the tegra drm driver not probing and thus nothing
> > being displayed on-screen.
>
> Fixes: 404bfb78daf3 ("gpu: host1x: Add IOMMU support")
>
> > Signed-off-by: Paul Kocialkowski <contact-
> > W9ppeneeCTY at public.gmane.org>
Tested-by:?Marcel Ziswiler <marcel.ziswiler@toradex.com>
Tested-on: Apalis TK1, Jetson-TK1
> > ---
> > ?arch/arm/boot/dts/tegra124.dtsi | 1 +
> > ?1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/boot/dts/tegra124.dtsi
> > b/arch/arm/boot/dts/tegra124.dtsi
> > index 187a36c6d0fc..b3b89befffeb 100644
> > --- a/arch/arm/boot/dts/tegra124.dtsi
> > +++ b/arch/arm/boot/dts/tegra124.dtsi
> > @@ -85,6 +85,7 @@
> > ? clocks = <&tegra_car TEGRA124_CLK_HOST1X>;
> > ? resets = <&tegra_car 28>;
> > ? reset-names = "host1x";
> > + iommus = <&mc TEGRA_SWGROUP_HC>;
> > ?
> > ? #address-cells = <2>;
> > ? #size-cells = <2>;
So I take it we still will need this one moving forward, correct?
How about tegra30, I guess the same applies there, isn't it? Should I
send a patch or are you guys doing that?
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"contact@paulk.fr" <contact@paulk.fr>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Cc: "jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"mperttunen@nvidia.com" <mperttunen@nvidia.com>,
"treding@nvidia.com" <treding@nvidia.com>,
"swarren@nvidia.com" <swarren@nvidia.com>
Subject: Re: [PATCH] ARM: tegra: Register host1x node with iommu binding on tegra124
Date: Tue, 11 Jul 2017 14:54:04 +0000 [thread overview]
Message-ID: <1499784841.1520.20.camel@toradex.com> (raw)
In-Reply-To: <1499763009.1340.11.camel@paulk.fr>
On Tue, 2017-07-11 at 11:50 +0300, Paul Kocialkowski wrote:
> On Sun, 2017-07-09 at 19:36 +0300, Paul Kocialkowski wrote:
> > This registers the host1x node with the SMMU (as HC swgroup) to
> > allow
> > the host1x code to attach to it. It avoid failing the probe
> > sequence,
> > which resulted in the tegra drm driver not probing and thus nothing
> > being displayed on-screen.
>
> Fixes: 404bfb78daf3 ("gpu: host1x: Add IOMMU support")
>
> > Signed-off-by: Paul Kocialkowski <contact-
> > W9ppeneeCTY@public.gmane.org>
Tested-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Tested-on: Apalis TK1, Jetson-TK1
> > ---
> > arch/arm/boot/dts/tegra124.dtsi | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/arch/arm/boot/dts/tegra124.dtsi
> > b/arch/arm/boot/dts/tegra124.dtsi
> > index 187a36c6d0fc..b3b89befffeb 100644
> > --- a/arch/arm/boot/dts/tegra124.dtsi
> > +++ b/arch/arm/boot/dts/tegra124.dtsi
> > @@ -85,6 +85,7 @@
> > clocks = <&tegra_car TEGRA124_CLK_HOST1X>;
> > resets = <&tegra_car 28>;
> > reset-names = "host1x";
> > + iommus = <&mc TEGRA_SWGROUP_HC>;
> >
> > #address-cells = <2>;
> > #size-cells = <2>;
So I take it we still will need this one moving forward, correct?
How about tegra30, I guess the same applies there, isn't it? Should I
send a patch or are you guys doing that?
next prev parent reply other threads:[~2017-07-11 14:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 16:36 [PATCH] ARM: tegra: Register host1x node with iommu binding on tegra124 Paul Kocialkowski
2017-07-09 16:36 ` Paul Kocialkowski
2017-07-09 16:36 ` Paul Kocialkowski
[not found] ` <20170709163614.6746-1-contact-W9ppeneeCTY@public.gmane.org>
2017-07-10 5:21 ` Thierry Reding
2017-07-10 5:21 ` Thierry Reding
2017-07-10 5:21 ` Thierry Reding
2017-07-10 6:05 ` Paul Kocialkowski
2017-07-10 6:05 ` Paul Kocialkowski
2017-07-10 6:05 ` Paul Kocialkowski
2017-07-11 8:50 ` Paul Kocialkowski
2017-07-11 8:50 ` Paul Kocialkowski
2017-07-11 8:50 ` Paul Kocialkowski
[not found] ` <1499763009.1340.11.camel-W9ppeneeCTY@public.gmane.org>
2017-07-11 14:54 ` Marcel Ziswiler [this message]
2017-07-11 14:54 ` Marcel Ziswiler
2017-07-11 14:54 ` Marcel Ziswiler
2017-07-11 15:05 ` Paul Kocialkowski
2017-07-11 15:05 ` Paul Kocialkowski
2017-07-11 15:05 ` Paul Kocialkowski
2017-07-11 15:17 ` Marcel Ziswiler
2017-07-11 15:17 ` Marcel Ziswiler
2017-07-31 15:23 ` Thierry Reding
2017-07-31 15:23 ` Thierry Reding
2017-08-01 9:56 ` Paul Kocialkowski
2017-08-01 9:56 ` Paul Kocialkowski
2017-08-01 9:56 ` Paul Kocialkowski
2017-07-31 14:48 ` Thierry Reding
2017-07-31 14:48 ` Thierry Reding
2017-07-31 14:48 ` Thierry Reding
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=1499784841.1520.20.camel@toradex.com \
--to=marcel.ziswiler-2kbjvhiyjgbbdgjk7y7tuq@public.gmane.org \
--cc=contact-W9ppeneeCTY@public.gmane.org \
--cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mperttunen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=treding-DDmLM1+adcrQT0dZR+AlfA@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 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.