From: Christoph Hellwig <hch@infradead.org>
To: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jun Nie <jun.nie@linaro.org>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 4/4] mmc: sdhci: Add DMA memory boundary workaround
Date: Tue, 3 Dec 2019 05:06:09 -0800 [thread overview]
Message-ID: <20191203130609.GA2144@infradead.org> (raw)
In-Reply-To: <20191203172434.39b2c2c2@xhacker.debian>
On Tue, Dec 03, 2019 at 09:49:49AM +0000, Jisheng Zhang wrote:
> > As in exactly one boundary and not an alignment? Where the one
> > boundary is not a power of two and thus can't be expressed?
>
> Take drivers/mmc/host/sdhci-of-dwcmshc.c for example, target physical DMA addr
> can't span 128MB, 256MB, 128*3MB, ...128*nMB
>
> I'm not sure whether blk_queue_segment_boundary could solve this limitation.
That is exaxtly the kind of limitation blk_queue_segment_boundary is
intended for.
next prev parent reply other threads:[~2019-12-03 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191202144104.5069-1-jun.nie@linaro.org>
[not found] ` <20191202144104.5069-5-jun.nie@linaro.org>
[not found] ` <20191203103320.273a7309@xhacker.debian>
[not found] ` <CABymUCMVi_N2Mt82YDt7wrys4Z_vnXYEu15-YBa+S1CejT9iZw@mail.gmail.com>
[not found] ` <20191203165123.4e6f9e28@xhacker.debian>
2019-12-03 9:18 ` [PATCH 4/4] mmc: sdhci: Add DMA memory boundary workaround Christoph Hellwig
2019-12-03 9:49 ` Jisheng Zhang
2019-12-03 13:06 ` Christoph Hellwig [this message]
2019-12-04 7:11 ` Jisheng Zhang
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=20191203130609.GA2144@infradead.org \
--to=hch@infradead.org \
--cc=Jisheng.Zhang@synaptics.com \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jun.nie@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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).