From: Yong Wu <yong.wu@mediatek.com>
To: <yf.wang@mediatek.com>
Cc: <wsd_upstream@mediatek.com>, Libo Kang <Libo.Kang@mediatek.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v3 0/2] MediaTek TTBR up to 35bit support
Date: Sat, 14 May 2022 10:09:27 +0800 [thread overview]
Message-ID: <65a0a606e5a53a4ca8dddbe59388c78280d60dd1.camel@mediatek.com> (raw)
In-Reply-To: <20220512144557.18025-1-yf.wang@mediatek.com>
On Thu, 2022-05-12 at 22:45 +0800, yf.wang@mediatek.com wrote:
> This patchset adds MediaTek TTBR up to 35bit support.
>
>
> Changes in v3:
> - Add version changes description, there is No new code change in V3.
>
> Changes in v2:
> - Update patch and commit message
> - Add Level 1 pgtable PA up to 35bit.
Why add this for lvl1 pgtable? Did you get real problem?
lvl2 pgtable is allocated/freed dynamically, it may be allocated failed
in ZONE_DMA32 when burning test. But the lvl1 pgtable only is allocated
once after bootup. I think this is no need for lvl1 pgtable.
> - This is new feature, remove stable@vger.kernel.org
> - Update commit message.
>
> Ning Li (2):
> iommu/io-pgtable-arm-v7s: Add a quirk to allow pgtable PA up to
> 35bit
> iomm/mediatek: Allow page table PA up to 35bit
>
> drivers/iommu/io-pgtable-arm-v7s.c | 56 ++++++++++++++++++++++----
> ----
> drivers/iommu/mtk_iommu.c | 29 +++++++++++++---
> include/linux/io-pgtable.h | 15 +++++---
> 3 files changed, 77 insertions(+), 23 deletions(-)
>
>
_______________________________________________
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:[~2022-05-14 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 14:45 [PATCH v3 0/2] MediaTek TTBR up to 35bit support yf.wang
2022-05-12 14:45 ` [PATCH v3 1/2] iommu/io-pgtable-arm-v7s: Add a quirk to allow pgtable PA up to 35bit yf.wang
2022-05-13 2:18 ` kernel test robot
2022-05-13 2:43 ` kernel test robot
2022-05-12 14:45 ` [PATCH v3 2/2] iomm/mediatek: Allow page table " yf.wang
2022-05-14 2:09 ` Yong Wu [this message]
2022-05-16 14:12 ` [PATCH v3 0/2] MediaTek TTBR up to 35bit support yf.wang
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=65a0a606e5a53a4ca8dddbe59388c78280d60dd1.camel@mediatek.com \
--to=yong.wu@mediatek.com \
--cc=Libo.Kang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=wsd_upstream@mediatek.com \
--cc=yf.wang@mediatek.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