From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Improve MMC performance on Versatile Express
Date: Mon, 24 Jan 2011 16:39:21 -0000 [thread overview]
Message-ID: <000101cbbbe5$45d47ed0$d17d7c70$@moll@arm.com> (raw)
In-Reply-To: <20110124162400.GC24104@n2100.arm.linux.org.uk>
> Given that the problem is already fixed via a set of patches, I see
> no reason to mess about with the hardware, thereby making the driver
> more complicated for *no* benefit.
There will be virtually no change in the driver - all required stuff is already there. See the STE UX500 variant - they did exactly the same, enlarged the FIFO. One of the main reason I've immediately abandoned the idea of using FIQ was the need of changing the driver for no good reason.
> Well, fixing MMCI because ISP1761 is buggy is not the way forward.
> The answer is to fix the broken ISP1761 driver.
Totally agree. The thing is that you are the only person right now who doesn't have any problems. The others can quickly benefit from the workaround. I think I made the status of this patch clear enough - let me quote myself: "HACK HACK HACK" ;-)
> Well as I see it, it's pointless enlarging the FIFO. ARM Ltd isn't
> going to give me updated FPGA images for the Integrator/CP, Versatile
> PB926, Realview EB and Versatile Express.
If we succeed with this, you (and all other users) will get the "improved" FPGA image. But for VE only indeed.
Pawe?
next prev parent reply other threads:[~2011-01-24 16:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 13:59 [PATCH] arm: Improve MMC performance on Versatile Express Pawel Moll
2011-01-21 15:09 ` Sergei Shtylyov
2011-01-21 19:59 ` Nicolas Pitre
2011-01-21 21:51 ` Russell King - ARM Linux
2011-01-21 22:20 ` Nicolas Pitre
2011-01-21 22:29 ` Russell King - ARM Linux
2011-02-01 14:29 ` Linus Walleij
2011-02-01 17:25 ` Pawel Moll
2011-01-24 12:27 ` Pawel Moll
2011-01-24 13:35 ` Russell King - ARM Linux
2011-01-24 16:13 ` Pawel Moll
2011-01-24 16:24 ` Russell King - ARM Linux
2011-01-24 16:30 ` Russell King - ARM Linux
2011-01-24 16:39 ` Pawel Moll [this message]
2011-01-24 16:53 ` Russell King - ARM Linux
2011-01-24 17:03 ` Russell King - ARM Linux
2011-01-24 17:54 ` Pawel Moll
2011-01-24 18:09 ` Russell King - ARM Linux
2011-01-24 19:59 ` Pawel Moll
2011-01-24 23:10 ` Russell King - ARM Linux
2011-02-01 11:18 ` Russell King - ARM Linux
2011-02-01 13:34 ` Pawel Moll
2011-02-01 14:28 ` Russell King - ARM Linux
2011-02-01 17:25 ` Pawel Moll
2011-02-03 14:15 ` Linus Walleij
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='000101cbbbe5$45d47ed0$d17d7c70$@moll@arm.com' \
--to=pawel.moll@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).