From: Christoph Hellwig <hch@infradead.org>
To: Vadym Kochan <vadym.kochan@plvision.eu>
Cc: Robin Murphy <robin.murphy@arm.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Christoph Hellwig <hch@infradead.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Hu Ziji <huziji@marvell.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Elad Nachman <enachman@marvell.com>,
iommu@lists.linux.dev, Mickey Rachamim <mickeyr@marvell.com>
Subject: Re: [PATCH] mmc: sdhci-xenon: Fix 2G limitation on AC5 SoC
Date: Sat, 20 Aug 2022 23:17:44 -0700 [thread overview]
Message-ID: <YwHOCHmKaf7yfgOD@infradead.org> (raw)
In-Reply-To: <20220818120740.GA21548@plvision.eu>
On Thu, Aug 18, 2022 at 03:07:40PM +0300, Vadym Kochan wrote:
> It works with the following changes:
>
> #1 dma-ranges = <0x0 0x0 0x2 0x0 0x0 0x80000000>;
>
> #3 swiotlb="force"
>
> Is it OK to force the memory allocation from the start for the swiotlb ?
It should be ok, but isn't really optimal.
I wonder if we should just allow DT to specify the swiotlb buffer
location. Basically have yet another RESERVEDMEM_OF_DECLARE variant
for it, which shouldn't be all that much work except for figuring
out the interaction with the various kernel command line options.
next prev parent reply other threads:[~2022-08-21 6:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 17:07 [PATCH] mmc: sdhci-xenon: Fix 2G limitation on AC5 SoC Vadym Kochan
2022-07-26 17:37 ` Florian Fainelli
2022-07-27 16:45 ` Vadym Kochan
2022-08-01 9:30 ` Vadym Kochan
2022-08-08 9:19 ` Adrian Hunter
2022-08-08 9:52 ` Vadym Kochan
2022-08-08 10:29 ` Vadym Kochan
2022-08-08 11:40 ` Adrian Hunter
2022-08-08 12:26 ` Vadym Kochan
2022-08-08 12:58 ` Adrian Hunter
2022-08-08 14:06 ` Robin Murphy
2022-08-16 20:51 ` Vadym Kochan
2022-08-17 13:43 ` Robin Murphy
2022-08-17 16:07 ` Vadym Kochan
2022-08-17 17:23 ` Robin Murphy
2022-08-18 12:07 ` Vadym Kochan
2022-08-21 6:17 ` Christoph Hellwig [this message]
2022-08-22 10:06 ` Robin Murphy
2022-09-06 9:22 ` Vadym Kochan
2022-10-13 6:40 ` Vadym Kochan
2022-11-08 19:05 ` Vadym Kochan
2022-11-09 7:50 ` Adrian Hunter
2022-11-09 8:40 ` Vadym Kochan
2022-11-09 9:29 ` Adrian Hunter
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=YwHOCHmKaf7yfgOD@infradead.org \
--to=hch@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=enachman@marvell.com \
--cc=f.fainelli@gmail.com \
--cc=huziji@marvell.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mickeyr@marvell.com \
--cc=robin.murphy@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=vadym.kochan@plvision.eu \
/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).