From: Eric Anholt <eric@anholt.net>
To: Gerd Hoffmann <kraxel@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: [PATCH 2/2] mmc: sdhci-iproc: Increase max_blk_size for bcm2835
Date: Tue, 03 Jan 2017 10:04:28 -0800 [thread overview]
Message-ID: <87o9zonhoz.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1483111474-29907-3-git-send-email-stefan.wahren@i2se.com>
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
Stefan Wahren <stefan.wahren@i2se.com> writes:
> According to the BCM2835 datasheet the maximum block size for the
> eMMC module is restricted to the internal data FIFO which is 1024 byte.
> But this is still an improvement to the default of 512 byte.
Confirmed that the internal FIFOs are 1k.
Reviewed-by: Eric Anholt <eric@anholt.net>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-01-03 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 15:24 [PATCH 0/2] mmc: sdhci-iproc: Improve bcm2835 performance Stefan Wahren
2016-12-30 15:24 ` [PATCH 1/2] mmc: sdhci-iproc: Apply caps from bcm2835-mmc driver Stefan Wahren
2017-01-03 18:27 ` Eric Anholt
2017-01-03 20:23 ` Stefan Wahren
2017-01-04 18:16 ` Eric Anholt
2017-01-05 9:53 ` Adrian Hunter
2016-12-30 15:24 ` [PATCH 2/2] mmc: sdhci-iproc: Increase max_blk_size for bcm2835 Stefan Wahren
2017-01-03 18:04 ` Eric Anholt [this message]
2017-01-04 18:47 ` Scott Branden
2017-01-05 9:53 ` Adrian Hunter
2017-01-10 15:38 ` [PATCH 0/2] mmc: sdhci-iproc: Improve bcm2835 performance Ulf Hansson
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=87o9zonhoz.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=adrian.hunter@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jonmason@broadcom.com \
--cc=kraxel@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--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