From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: David Jander <david@protonic.nl>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Pierre Ossman <pierre@ossman.eu>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Lucas Stach <l.stach@pengutronix.de>
Subject: Re: SDHCI long sleep with interrupts off
Date: Fri, 18 Dec 2015 18:38:43 +0000 [thread overview]
Message-ID: <20151218183843.GP8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20151217132229.1c699f69@archvile>
On Thu, Dec 17, 2015 at 01:22:29PM +0100, David Jander wrote:
> Ok, this sounds like a good way to go. Unfortunately it also sounds like a
> major endeavor, for which good knowledge of the SDHCI standard is necessary.
That's not entirely true.
Anyone who is really good at programming can fix this: it's a matter of
making changes via a series of code transformations which allow you to
reach a goal.
As far as I can see, there's two solutions to SDHCI:
1. We chuck the existing crappy driver away and start over.
2. We change the existing driver to improve it, which requires the
transformation approach.
When I say "transformation", it's about making just one change at a time,
such as creating a new function which contains shared code, and then
arranging for it to be called.
The series I did (starting at da91a8f9c0f5) is most likely done via
this method - when modifying a complex driver, I think it's the only
way to make changes safely. The approach has many advantages, the
most important is that the changes should look obvious and trivial,
even though the sum of the changes may be complex.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-12-18 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 10:28 SDHCI long sleep with interrupts off David Jander
2015-12-17 11:03 ` Lucas Stach
2015-12-17 11:20 ` David Jander
2015-12-17 11:27 ` Lucas Stach
2015-12-17 11:39 ` Ulf Hansson
2015-12-17 12:22 ` David Jander
2015-12-17 14:54 ` Ulf Hansson
2015-12-17 15:09 ` David Jander
2015-12-18 20:09 ` Russell King - ARM Linux
2015-12-18 18:38 ` Russell King - ARM Linux [this message]
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=20151218183843.GP8644@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=david@protonic.nl \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=pierre@ossman.eu \
--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