From: Robin Murphy <robin.murphy@arm.com>
To: Will Deacon <will@kernel.org>, Neil Armstrong <narmstrong@baylibre.com>
Cc: robh@kernel.org, tomeu.vizoso@collabora.com, joro@8bytes.org,
steven.price@arm.com, iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] iommu/io-pgtable-arm: Mali LPAE improvements
Date: Wed, 11 Sep 2019 18:19:40 +0100 [thread overview]
Message-ID: <83c45e97-8398-349d-5593-03af23b39c59@arm.com> (raw)
In-Reply-To: <20190911162024.i2sda7uzy3pbrnyd@willie-the-truck>
On 2019-09-11 5:20 pm, Will Deacon wrote:
> On Wed, Sep 11, 2019 at 06:19:04PM +0200, Neil Armstrong wrote:
>> On 11/09/2019 16:42, Robin Murphy wrote:
>>> Here's the eagerly-awaited fix to unblock T720/T820, plus a couple of
>>> other bits that I've collected so far. I'm not considering this as
>>> 5.3 fixes material, but it would be nice if there's any chance still
>>> to sneak it into 5.4.
>>>
>>> Robin.
>>>
>>>
>>> Robin Murphy (3):
>>> iommu/io-pgtable-arm: Correct Mali attributes
>>> iommu/io-pgtable-arm: Support more Mali configurations
>>> iommu/io-pgtable-arm: Allow coherent walks for Mali
>>>
>>> drivers/iommu/io-pgtable-arm.c | 61 ++++++++++++++++++++++++++--------
>>> 1 file changed, 48 insertions(+), 13 deletions(-)
>>>
>>
>> Tested-by: Neil Armstrong <narmstrong@baylibre.com>
>>
>> On Khadas VIM2 (Amlogic S912) with T820 Mali GPU
>>
>> I hope this will be part of v5.4 so we can run panfrost on vanilla v5.4 !
>
> Not a chance -- the merge window opens on Monday and -next isn't being
> rolled out at the moment due to LPC. Let's shoot for 5.5 and get this
> queued up in a few weeks.
Fair enough, that was certainly more extreme optimism than realistic
expectation on my part :)
There is some argument for taking #1 and #2 as 5.4 fixes, though - the
upcoming Mesa 19.2 release will enable T820 support on the userspace
side - so let's pick that discussion up again in a few weeks.
Robin.
(And at worst, I guess we could carry the "cfg.ias = 48" workaround in
the DRM driver for the 5.4 cycle if need be)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-11 17:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 14:42 [PATCH 0/3] iommu/io-pgtable-arm: Mali LPAE improvements Robin Murphy
2019-09-11 14:42 ` [PATCH 1/3] iommu/io-pgtable-arm: Correct Mali attributes Robin Murphy
2019-09-12 10:41 ` Steven Price
2019-09-11 14:42 ` [PATCH 2/3] iommu/io-pgtable-arm: Support more Mali configurations Robin Murphy
2019-09-12 10:47 ` Steven Price
2019-09-11 14:42 ` [PATCH 3/3] iommu/io-pgtable-arm: Allow coherent walks for Mali Robin Murphy
2019-09-12 10:53 ` Steven Price
2019-09-11 16:19 ` [PATCH 0/3] iommu/io-pgtable-arm: Mali LPAE improvements Neil Armstrong
2019-09-11 16:20 ` Will Deacon
2019-09-11 17:19 ` Robin Murphy [this message]
2019-09-19 8:30 ` Will Deacon
2019-09-23 8:17 ` Tomeu Vizoso
2019-09-23 11:04 ` Robin Murphy
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=83c45e97-8398-349d-5593-03af23b39c59@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=narmstrong@baylibre.com \
--cc=robh@kernel.org \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).