From: Catalin Marinas <catalin.marinas@arm.com>
To: Phil Chang <phil.chang@mediatek.com>
Cc: linux-arm-kernel@lists.infradead.org,
Jonathan Corbet <corbet@lwn.net>, Will Deacon <will@kernel.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
YJ Chiang <yj.chiang@mediatek.com>,
Alix Wu <alix.wu@mediatek.com>, Mike Rapoport <rppt@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] [PATCH] ARM64: Setup DMA32 zone size by bootargs
Date: Tue, 15 Sep 2020 17:13:44 +0100 [thread overview]
Message-ID: <20200915161344.GD14908@gaia> (raw)
In-Reply-To: <20200915150855.24825-1-phil.chang@mediatek.com>
On Tue, Sep 15, 2020 at 11:08:55PM +0800, Phil Chang wrote:
> Allowing the DMA32 zone be configurable in ARM64 but at most 4Gb.
Why? What is your use-case?
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Phil Chang <phil.chang@mediatek.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Alix Wu <alix.wu@mediatek.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
YJ Chiang <yj.chiang@mediatek.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Mike Rapoport <rppt@kernel.org>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] [PATCH] ARM64: Setup DMA32 zone size by bootargs
Date: Tue, 15 Sep 2020 17:13:44 +0100 [thread overview]
Message-ID: <20200915161344.GD14908@gaia> (raw)
In-Reply-To: <20200915150855.24825-1-phil.chang@mediatek.com>
On Tue, Sep 15, 2020 at 11:08:55PM +0800, Phil Chang wrote:
> Allowing the DMA32 zone be configurable in ARM64 but at most 4Gb.
Why? What is your use-case?
--
Catalin
_______________________________________________
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: Catalin Marinas <catalin.marinas@arm.com>
To: Phil Chang <phil.chang@mediatek.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Alix Wu <alix.wu@mediatek.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
YJ Chiang <yj.chiang@mediatek.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Mike Rapoport <rppt@kernel.org>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] [PATCH] ARM64: Setup DMA32 zone size by bootargs
Date: Tue, 15 Sep 2020 17:13:44 +0100 [thread overview]
Message-ID: <20200915161344.GD14908@gaia> (raw)
In-Reply-To: <20200915150855.24825-1-phil.chang@mediatek.com>
On Tue, Sep 15, 2020 at 11:08:55PM +0800, Phil Chang wrote:
> Allowing the DMA32 zone be configurable in ARM64 but at most 4Gb.
Why? What is your use-case?
--
Catalin
_______________________________________________
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:[~2020-09-15 22:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 15:08 [PATCH] [PATCH] ARM64: Setup DMA32 zone size by bootargs Phil Chang
2020-09-15 15:08 ` Phil Chang
2020-09-15 15:08 ` Phil Chang
2020-09-15 16:13 ` Catalin Marinas [this message]
2020-09-15 16:13 ` Catalin Marinas
2020-09-15 16:13 ` Catalin Marinas
2020-09-15 16:18 ` Mike Rapoport
2020-09-15 16:18 ` Mike Rapoport
2020-09-15 16:18 ` Mike Rapoport
2020-09-15 17:48 ` David Woodhouse
2020-09-15 17:48 ` David Woodhouse
2020-09-15 17:48 ` David Woodhouse
2020-09-16 7:22 ` Phil Chang
2020-09-16 7:22 ` Phil Chang
2020-09-16 7:22 ` Phil Chang
2020-09-16 8:37 ` Christoph Hellwig
2020-09-16 8:37 ` Christoph Hellwig
2020-09-16 8:37 ` Christoph Hellwig
2020-09-16 13:33 ` Phil Chang
2020-09-16 13:33 ` Phil Chang
2020-09-16 13:33 ` Phil Chang
2020-09-16 14:56 ` Catalin Marinas
2020-09-16 14:56 ` Catalin Marinas
2020-09-16 14:56 ` Catalin Marinas
2020-09-24 14:15 ` Phil Chang
2020-09-24 14:15 ` Phil Chang
2020-09-24 14:15 ` Phil Chang
2020-09-25 9:11 ` Catalin Marinas
2020-09-25 9:11 ` Catalin Marinas
2020-09-25 9:11 ` Catalin Marinas
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=20200915161344.GD14908@gaia \
--to=catalin.marinas@arm.com \
--cc=alix.wu@mediatek.com \
--cc=anshuman.khandual@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchehab+huawei@kernel.org \
--cc=phil.chang@mediatek.com \
--cc=rppt@kernel.org \
--cc=will@kernel.org \
--cc=yj.chiang@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.