From: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] iommu/rockchip: Make use of 'struct iommu_device'
Date: Mon, 03 Apr 2017 13:11:01 +0200 [thread overview]
Message-ID: <4252325.o7BCCiZe8L@diego> (raw)
In-Reply-To: <20170403110758.GB4683-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Am Montag, 3. April 2017, 13:07:58 CEST schrieb Joerg Roedel:
> Hey Heiko,
>
> On Mon, Apr 03, 2017 at 11:56:59AM +0200, Heiko Stübner wrote:
> > In general works, and I still keep a working iommu-based display :-)
> > I can also see my two vop iommus under /sys/class/iommu now.
>
> Great, thanks for testing that patch!
>
> > Links in the devices subdirectory do not work though, see below:
> Okay, thats bad, but I think its nothing we should work around right
> now. My goal with this work is to have a per-iommu check-device
> call-back to bind devices to iommus in the core code.
>
> This will also solve the probe-ordering issue and we are fine again. We
> just call check-device then for every device on the bus that has no
> iommu already when the iommu is registered and create the links at that
> time.
ok, so you can at least add my
Tested-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
on the patch
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu/rockchip: Make use of 'struct iommu_device'
Date: Mon, 03 Apr 2017 13:11:01 +0200 [thread overview]
Message-ID: <4252325.o7BCCiZe8L@diego> (raw)
In-Reply-To: <20170403110758.GB4683@8bytes.org>
Am Montag, 3. April 2017, 13:07:58 CEST schrieb Joerg Roedel:
> Hey Heiko,
>
> On Mon, Apr 03, 2017 at 11:56:59AM +0200, Heiko St?bner wrote:
> > In general works, and I still keep a working iommu-based display :-)
> > I can also see my two vop iommus under /sys/class/iommu now.
>
> Great, thanks for testing that patch!
>
> > Links in the devices subdirectory do not work though, see below:
> Okay, thats bad, but I think its nothing we should work around right
> now. My goal with this work is to have a per-iommu check-device
> call-back to bind devices to iommus in the core code.
>
> This will also solve the probe-ordering issue and we are fine again. We
> just call check-device then for every device on the bus that has no
> iommu already when the iommu is registered and create the links at that
> time.
ok, so you can at least add my
Tested-by: Heiko Stuebner <heiko@sntech.de>
on the patch
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Joerg Roedel <joro@8bytes.org>
Cc: iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH] iommu/rockchip: Make use of 'struct iommu_device'
Date: Mon, 03 Apr 2017 13:11:01 +0200 [thread overview]
Message-ID: <4252325.o7BCCiZe8L@diego> (raw)
In-Reply-To: <20170403110758.GB4683@8bytes.org>
Am Montag, 3. April 2017, 13:07:58 CEST schrieb Joerg Roedel:
> Hey Heiko,
>
> On Mon, Apr 03, 2017 at 11:56:59AM +0200, Heiko Stübner wrote:
> > In general works, and I still keep a working iommu-based display :-)
> > I can also see my two vop iommus under /sys/class/iommu now.
>
> Great, thanks for testing that patch!
>
> > Links in the devices subdirectory do not work though, see below:
> Okay, thats bad, but I think its nothing we should work around right
> now. My goal with this work is to have a per-iommu check-device
> call-back to bind devices to iommus in the core code.
>
> This will also solve the probe-ordering issue and we are fine again. We
> just call check-device then for every device on the bus that has no
> iommu already when the iommu is registered and create the links at that
> time.
ok, so you can at least add my
Tested-by: Heiko Stuebner <heiko@sntech.de>
on the patch
Heiko
next prev parent reply other threads:[~2017-04-03 11:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 14:30 [PATCH] iommu/rockchip: Make use of 'struct iommu_device' Joerg Roedel
2017-03-31 14:30 ` Joerg Roedel
2017-03-31 14:30 ` Joerg Roedel
2017-04-03 9:56 ` Heiko Stübner
2017-04-03 9:56 ` Heiko Stübner
2017-04-03 11:07 ` Joerg Roedel
2017-04-03 11:07 ` Joerg Roedel
2017-04-03 11:07 ` Joerg Roedel
[not found] ` <20170403110758.GB4683-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-04-03 11:11 ` Heiko Stübner [this message]
2017-04-03 11:11 ` Heiko Stübner
2017-04-03 11:11 ` Heiko Stübner
2017-04-03 11:18 ` Joerg Roedel
2017-04-03 11:18 ` Joerg Roedel
2017-04-03 11:18 ` 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=4252325.o7BCCiZe8L@diego \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=jroedel-l3A5Bk7waGM@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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.