From: Jon Hunter <jonathanh@nvidia.com>
To: Mikko Perttunen <cyndis@kapsi.fi>,
Paul Kocialkowski <contact@paulk.fr>,
<linux-arm-kernel@lists.infradead.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: Re: [PATCH] gpu: host1x: Free the IOMMU domain when there is no device to attach
Date: Tue, 18 Jul 2017 10:09:45 +0100 [thread overview]
Message-ID: <8db74bfc-e442-dd32-4b24-1c33f3a82d92@nvidia.com> (raw)
In-Reply-To: <09ecbf74-ac5d-a7f5-c6bd-53f4f84a0de5@kapsi.fi>
Hi Mikko,
On 11/07/17 07:43, Mikko Perttunen wrote:
> Thanks for the patch, didn't consider this case. I really need to get
> together some system to automatically test on multiple platforms.. :)
We already have the infrastructure in place to do this, however, at the
moment we are just making sure the platforms boot. Something like this
we should be able to catch, even if we don't explicitly test display/hdmi.
I was thinking that we could parse the /dev and /sys file-systems to
ensure that devices for a given platform are present after boot. I am
not sure if there is a good way to do this, but if you have any
thoughts, then I am willing to add more testing.
What is interesting about this case, was that there were no specific
error messages that indicated this had broken AFAICT.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2017-07-18 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 19:33 Paul Kocialkowski
2017-07-11 6:43 ` Mikko Perttunen
2017-07-18 9:09 ` Jon Hunter [this message]
2017-07-11 8:49 ` Paul Kocialkowski
2017-07-11 14:37 ` Marcel Ziswiler
2017-07-11 14:44 ` Paul Kocialkowski
2017-07-11 17:09 ` Mikko Perttunen
2017-07-27 16:45 ` 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=8db74bfc-e442-dd32-4b24-1c33f3a82d92@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=contact@paulk.fr \
--cc=cyndis@kapsi.fi \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®