From: Stephen Warren <swarren@wwwdotorg.org>
To: Eric Anholt <eric@anholt.net>
Cc: linux-rpi-kernel@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Lee Jones <lee@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH 2/3] ARM: multi_v7_defconfig: Switch BCM2835 to sdhci-iproc.c for MMC
Date: Fri, 1 Apr 2016 10:58:34 -0600 [thread overview]
Message-ID: <56FEA8BA.8020307@wwwdotorg.org> (raw)
In-Reply-To: <56FDD697.2050901@wwwdotorg.org>
On 03/31/2016 08:01 PM, Stephen Warren wrote:
> On 03/31/2016 06:28 PM, Eric Anholt wrote:
>> This approximately triples write performance for the SD card. My card
>> is too full of important data to collect very reliable numbers, but I
>> see 271.361% +/- 166.742% improvement (n=3 before, 6 after), for 'dd
>> if=/dev/zero of=/boot/asdf bs=1M count=3 oflag=dsync,direct'. Read
>> performance appears to be unaffected.
>
> I thought that switching the defconfig wasn't possible, since this HW
> module relies on the SoC core clock, and that can be asynchronously
> changed by the FW running on the VideoCore. Consequently, this change
> isn't safe unless the user puts non-default options in their config.txt.
>
> The same comment applies to "[PATCH 1/4] ARM: bcm2835: Switch BCM2835 to
> sdhci-iproc.c for MMC" in the other series.
Ah, now I realize that sdhci-bcm2835.c and sdhci-iproc.c are two
alternative drivers for the same HW device. For some reason I got the
incorrect impression from some past email/patch discussion that
sdhci-iproc.c was a driver for the alternative SD controller in the chip.
So, there's no problem with this patch.
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
(although /me wonders why sdhci-iproc.c was even added in the first
place given sdhci-bcm2835.c pre-dates it by over 2 years, and equally
why the new driver is any faster given it looks almost identical and
accesses the same HW, but I suppose it doesn't matter).
next prev parent reply other threads:[~2016-04-01 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 0:28 [PATCH 1/3] ARM: multi_v7_defconfig: Add more BCM2835 support Eric Anholt
2016-04-01 0:28 ` [PATCH 2/3] ARM: multi_v7_defconfig: Switch BCM2835 to sdhci-iproc.c for MMC Eric Anholt
2016-04-01 2:01 ` Stephen Warren
2016-04-01 15:48 ` Eric Anholt
2016-04-01 16:58 ` Stephen Warren [this message]
2016-04-01 20:17 ` Stefan Wahren
2016-04-01 0:28 ` [PATCH 3/3] ARM: multi_v7_defconfig: Build in DWC2 USB support Eric Anholt
2016-04-01 2:04 ` [PATCH 1/3] ARM: multi_v7_defconfig: Add more BCM2835 support Stephen Warren
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=56FEA8BA.8020307@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
/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