From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
Mikko Perttunen <mperttunen@nvidia.com>
Subject: Re: [PATCH 2/2] drm/tegra: Acquire a reference to the IOVA cache
Date: Mon, 23 Apr 2018 11:43:16 +0300 [thread overview]
Message-ID: <c07b8a6a-3509-74d0-17a1-f7ace40f532b@gmail.com> (raw)
In-Reply-To: <ae552ade-e4e7-669c-ee85-820a92490871@gmail.com>
On 23.04.2018 11:41, Dmitry Osipenko wrote:
> On 23.04.2018 11:34, Dmitry Osipenko wrote:
>> On 23.04.2018 09:57, Thierry Reding wrote:
>>> From: Thierry Reding <treding@nvidia.com>
>>>
>>> The IOVA API uses a memory cache to allocate IOVA nodes from. To make
>>> sure that this cache is available, obtain a reference to it and release
>>> the reference when the cache is no longer needed.
>>>
>>> On 64-bit ARM this is hidden by the fact that the DMA mapping API gets
>>> that reference and never releases it. On 32-bit ARM, however, the DMA
>>> mapping API doesn't do that, so allocation of IOVA nodes fails.
>>>
>>> Signed-off-by: Thierry Reding <treding@nvidia.com>
>>> ---
>>
>> Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
>> Tested-by: Dmitry Osipenko <digetx@gmail.com>
>>
>> CONFIG_TEGRA_IOMMU_SMMU is enabled in the default kernel configs and hence DRM
>> should fail to probe on t124 since 4.11. What about to add stable tag for v4.11+
>> here to unbreak stable kernels as well?
>
> IOMMU node for host1x was added to t124 DT in kernel v4.14, so s/4.11/4.14/.
On the other hand nothing stops to use newer DT with older kernel.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-23 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 6:57 [PATCH 1/2] drm/tegra: Fix order of teardown in IOMMU case Thierry Reding
2018-04-23 6:57 ` [PATCH 2/2] drm/tegra: Acquire a reference to the IOVA cache Thierry Reding
2018-04-23 8:34 ` Dmitry Osipenko
2018-04-23 8:41 ` Dmitry Osipenko
2018-04-23 8:43 ` Dmitry Osipenko [this message]
2018-05-14 9:02 ` Thierry Reding
2018-05-17 10:53 ` Dmitry Osipenko
2018-05-17 12:09 ` Thierry Reding
2018-04-23 8:35 ` [PATCH 1/2] drm/tegra: Fix order of teardown in IOMMU case Dmitry Osipenko
2018-05-14 8:59 ` 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=c07b8a6a-3509-74d0-17a1-f7ace40f532b@gmail.com \
--to=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--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 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.