All of lore.kernel.org
 help / color / mirror / Atom feed
From: <yf.wang@mediatek.com>
To: <yong.wu@mediatek.com>
Cc: <Libo.Kang@mediatek.com>, <linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
	<wsd_upstream@mediatek.com>, <yf.wang@mediatek.com>
Subject: Re: [PATCH v3 0/2] MediaTek TTBR up to 35bit support
Date: Mon, 16 May 2022 22:12:02 +0800	[thread overview]
Message-ID: <20220516141202.11650-1-yf.wang@mediatek.com> (raw)
In-Reply-To: <65a0a606e5a53a4ca8dddbe59388c78280d60dd1.camel@mediatek.com>

On Sat, 2022-05-14 at 10:09 +0800, Yong Wu wrote:
> 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.

Hi Yong,

There is no DMA32 zone in some mediatek smartphone chip.

Thanks,
Yunfei.

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: <yf.wang@mediatek.com>
To: <yong.wu@mediatek.com>
Cc: <Libo.Kang@mediatek.com>, <linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
	<wsd_upstream@mediatek.com>, <yf.wang@mediatek.com>
Subject: Re: [PATCH v3 0/2] MediaTek TTBR up to 35bit support
Date: Mon, 16 May 2022 22:12:02 +0800	[thread overview]
Message-ID: <20220516141202.11650-1-yf.wang@mediatek.com> (raw)
In-Reply-To: <65a0a606e5a53a4ca8dddbe59388c78280d60dd1.camel@mediatek.com>

On Sat, 2022-05-14 at 10:09 +0800, Yong Wu wrote:
> 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.

Hi Yong,

There is no DMA32 zone in some mediatek smartphone chip.

Thanks,
Yunfei.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-05-16 14:19 UTC|newest]

Thread overview: 22+ 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 ` 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-12 14:45   ` yf.wang
2022-05-12 14:45   ` yf.wang
2022-05-12 14:45   ` yf.wang--- via iommu
2022-05-13  2:18   ` kernel test robot
2022-05-13  2:18     ` kernel test robot
2022-05-13  2:18     ` kernel test robot
2022-05-13  2:18     ` kernel test robot
2022-05-13  2:43   ` kernel test robot
2022-05-13  2:43     ` kernel test robot
2022-05-13  2:43     ` 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-12 14:45   ` yf.wang
2022-05-12 14:45   ` yf.wang
2022-05-12 14:45   ` yf.wang--- via iommu
2022-05-14  2:09 ` [PATCH v3 0/2] MediaTek TTBR up to 35bit support Yong Wu
2022-05-14  2:09   ` Yong Wu
2022-05-16 14:12   ` yf.wang [this message]
2022-05-16 14:12     ` 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=20220516141202.11650-1-yf.wang@mediatek.com \
    --to=yf.wang@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=yong.wu@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 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.