From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: "kernelci-results@groups.io" <kernelci-results@groups.io>,
linux-kernel@vger.kernel.org, jonathanh@nvidia.com,
iommu@lists.linux-foundation.org, thierry.reding@gmail.com,
linux-tegra@vger.kernel.org, Dmitry Osipenko <digetx@gmail.com>,
kernel@collabora.com, will@kernel.org
Subject: Re: [PATCH RESEND v2 4/5] iommu/tegra-smmu: Rework tegra_smmu_probe_device()
Date: Thu, 4 Feb 2021 21:24:23 -0800 [thread overview]
Message-ID: <20210205052422.GA11329@Asurada-Nvidia> (raw)
In-Reply-To: <46a96cf9-91cc-2ad4-702a-e95ba7200375@collabora.com>
Hi Guillaume,
On Thu, Feb 04, 2021 at 11:10:15AM +0000, Guillaume Tucker wrote:
> Hi Nicolin,
>
> A regression was detected by kernelci.org in IGT's drm_read tests
> on mainline, it was first seen on 17th December 2020. You can
> find some details here:
>
> https://kernelci.org/test/case/id/600b82dc1e3208f123d3dffc/
Thanks for reporting the issue. We did test on Tegra210 and Tegra30
yet not on Tegra124. I am wondering what could go wrong...
> Please let us know if you need any help debugging this issue or
> to try a fix on this platform.
Yes, I don't have any Tegra124 platform to run. It'd be very nice
if you can run some debugging patch (I can provide you) and a fix
after I root cause the issue.
Thanks
Nicolin
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: will@kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-tegra@vger.kernel.org,
jonathanh@nvidia.com, vdumpa@nvidia.com,
thierry.reding@gmail.com, joro@8bytes.org, kernel@collabora.com,
Dmitry Osipenko <digetx@gmail.com>,
"kernelci-results@groups.io" <kernelci-results@groups.io>
Subject: Re: [PATCH RESEND v2 4/5] iommu/tegra-smmu: Rework tegra_smmu_probe_device()
Date: Thu, 4 Feb 2021 21:24:23 -0800 [thread overview]
Message-ID: <20210205052422.GA11329@Asurada-Nvidia> (raw)
In-Reply-To: <46a96cf9-91cc-2ad4-702a-e95ba7200375@collabora.com>
Hi Guillaume,
On Thu, Feb 04, 2021 at 11:10:15AM +0000, Guillaume Tucker wrote:
> Hi Nicolin,
>
> A regression was detected by kernelci.org in IGT's drm_read tests
> on mainline, it was first seen on 17th December 2020. You can
> find some details here:
>
> https://kernelci.org/test/case/id/600b82dc1e3208f123d3dffc/
Thanks for reporting the issue. We did test on Tegra210 and Tegra30
yet not on Tegra124. I am wondering what could go wrong...
> Please let us know if you need any help debugging this issue or
> to try a fix on this platform.
Yes, I don't have any Tegra124 platform to run. It'd be very nice
if you can run some debugging patch (I can provide you) and a fix
after I root cause the issue.
Thanks
Nicolin
next prev parent reply other threads:[~2021-02-05 5:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 10:10 [PATCH RESEND v2 0/5] iommu/tegra-smmu: Some pending reviewed changes Nicolin Chen
2020-11-25 10:10 ` Nicolin Chen
2020-11-25 10:10 ` [PATCH RESEND v2 1/5] iommu/tegra-smmu: Unwrap tegra_smmu_group_get Nicolin Chen
2020-11-25 10:10 ` Nicolin Chen
2020-11-25 10:10 ` [PATCH RESEND v2 2/5] iommu/tegra-smmu: Expand mutex protection range Nicolin Chen
2020-11-25 10:10 ` Nicolin Chen
2020-11-25 10:10 ` [PATCH RESEND v2 3/5] iommu/tegra-smmu: Use fwspec in tegra_smmu_(de)attach_dev Nicolin Chen
2020-11-25 10:10 ` Nicolin Chen
2020-11-25 10:10 ` [PATCH RESEND v2 4/5] iommu/tegra-smmu: Rework tegra_smmu_probe_device() Nicolin Chen
2020-11-25 10:10 ` Nicolin Chen
2021-02-04 11:10 ` Guillaume Tucker
2021-02-04 11:10 ` Guillaume Tucker
2021-02-05 5:24 ` Nicolin Chen [this message]
2021-02-05 5:24 ` Nicolin Chen
2021-02-05 9:45 ` Nicolin Chen
2021-02-05 9:45 ` Nicolin Chen
2021-02-06 13:40 ` Guillaume Tucker
2021-02-06 13:40 ` Guillaume Tucker
2021-02-10 8:20 ` Nicolin Chen
2021-02-10 8:20 ` Nicolin Chen
2021-02-11 15:50 ` Guillaume Tucker
2021-02-11 15:50 ` Guillaume Tucker
2021-02-18 10:35 ` Nicolin Chen
2021-02-18 10:35 ` Nicolin Chen
2021-02-18 20:38 ` Guillaume Tucker
2021-02-18 20:38 ` Guillaume Tucker
2020-11-25 10:10 ` [PATCH RESEND v2 5/5] iommu/tegra-smmu: Add PCI support Nicolin Chen
2020-11-25 10:10 ` Nicolin Chen
2020-11-25 11:03 ` [PATCH RESEND v2 0/5] iommu/tegra-smmu: Some pending reviewed changes Will Deacon
2020-11-25 11:03 ` Will Deacon
2020-11-25 14:05 ` Will Deacon
2020-11-25 14:05 ` Will Deacon
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=20210205052422.GA11329@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=digetx@gmail.com \
--cc=guillaume.tucker@collabora.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathanh@nvidia.com \
--cc=kernel@collabora.com \
--cc=kernelci-results@groups.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=will@kernel.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.