From: colin.tuckley@arm.com (Colin Tuckley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: RealView SD/MMC Card detection and write-protect using GPIOLIB
Date: Tue, 26 Jan 2010 08:23:24 -0000 [thread overview]
Message-ID: <000001ca9e60$d4487d90$9fca010a@Emea.Arm.com> (raw)
In-Reply-To: <20100125180440.GD22481@n2100.arm.linux.org.uk>
> -----Original Message-----
> From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> No; if it's broken then it's because something's wrong, and I
> think there
> was a mail about that recently. I don't particularly like
> forcing options
> on when there's better solutions to the problem (like fixing
> the cause of
> the actual breakage.)
Actually, the patch description is slightly wrong/misleading.
The original patch did break the card detection on some boards. Also the
configuration options mentioned do need setting for things to work properly.
I think it's that the PL061 driver didn't get included in the kernel by the
original patch. Maybe it should be added to the realview_default config
files?
The problem here I think is that someone implemented gpiolib for sdcard
detection on mach-realview without doing any testing. When I started working
on a kernel with gpiolib I found the detection broken. After a lot of
experimentation and discussion with Catalin we decided that the patch I
submitted was the best way forward.
If it's not acceptable please suggest something that is.
Colin
--
Colin Tuckley - ARM Ltd.
110 Fulbourn Rd
Cambridge, CB1 9NJ
Tel: +44 1223 400536
next prev parent reply other threads:[~2010-01-26 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 12:58 [PATCH] ARM: RealView SD/MMC Card detection and write-protect using GPIOLIB Colin Tuckley
2010-01-25 18:04 ` Russell King - ARM Linux
2010-01-26 8:23 ` Colin Tuckley [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-16 15:31 Colin Tuckley
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='000001ca9e60$d4487d90$9fca010a@Emea.Arm.com' \
--to=colin.tuckley@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).