LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Will Newton <will.newton@gmail.com>
Cc: Chris Ball <cjb@laptop.org>,
Matt Fleming <matt@console-pimps.org>,
linux-mmc@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dw_mmc: Add Synopsys DesignWare mmc host driver.
Date: Sun, 12 Dec 2010 14:47:50 +0000 [thread overview]
Message-ID: <20101212144750.GH8665@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTin++a_juBQDssFDd881R449so7Um2AvHFLXqiT_@mail.gmail.com>
On Sun, Dec 12, 2010 at 02:31:40PM +0000, Will Newton wrote:
> On Sun, Dec 12, 2010 at 2:11 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > Maybe invent CONFIG_HAVE_MMIO_64BIT which architectures can select as
> > appropriate?
>
> Wouldn't it be simpler to have a fallback readq/writeq implementation
> like the below?
>
> static inline u64 __raw_readq(const volatile void __iomem *addr)
> {
> return *(const volatile u64 __force *) addr;
> }
>
> It won't break any existing hardware (if your SoC bus does not support
> 64bit accesses you are unlikely to have peripherals that require it)
> and would avoid a number of #ifdefs and/or Kconfig dependencies.
Firstly, why, then, are we discussing fixing dw_mmc.c so it builds on ARM?
Just make its configuration option conditional on !ARM and that specific
problem is solved.
Secondly, providing such a fallback implementation is asking people to
use it, and they'll expect it to work. Their driver will build and
apparantly work, but because the compiler will use ldrd/strd for it, a
perfectly timed interrupt could cause data corruption.
It's unsafe to provide 64-bit MMIO operations on hardware which is unable
to perform 64-bit MMIO atomically - it will lead to really subtle driver
bugs.
next prev parent reply other threads:[~2010-12-12 14:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 15:53 [RESEND PATCH] " Will Newton
2010-12-08 11:55 ` Matt Fleming
2010-12-08 13:14 ` Will Newton
2010-12-08 14:21 ` [PATCH] " Will Newton
2010-12-08 16:07 ` Matt Fleming
2010-12-09 6:47 ` Chris Ball
2010-12-09 12:11 ` Will Newton
2010-12-09 16:01 ` Chris Ball
2010-12-09 17:24 ` Will Newton
[not found] ` <20101211192320.GA24430@void.printf.net>
2010-12-12 8:41 ` Russell King - ARM Linux
2010-12-12 11:15 ` Russell King - ARM Linux
2010-12-12 10:57 ` Will Newton
2010-12-12 13:52 ` Chris Ball
2010-12-12 14:03 ` Will Newton
2010-12-12 14:11 ` Russell King - ARM Linux
2010-12-12 14:31 ` Will Newton
2010-12-12 14:47 ` Russell King - ARM Linux [this message]
2010-12-12 15:17 ` Will Newton
2010-12-16 17:04 ` [PATCH v4] " Will Newton
2011-01-02 6:20 ` Chris Ball
2011-01-18 7:54 ` Jaehoon Chung
2011-01-18 10:21 ` Will Newton
2011-02-08 6:38 ` Jaehoon Chung
2011-02-08 10:29 ` Will Newton
2011-02-08 10:49 ` Jaehoon Chung
2011-02-08 12:06 ` Will Newton
2010-12-09 17:35 ` [PATCH] " Chris Ball
2010-12-09 17:46 ` Will Newton
-- strict thread matches above, loose matches on Subject: below --
2010-11-29 17:35 Will Newton
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=20101212144750.GH8665@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=will.newton@gmail.com \
--subject='Re: [PATCH] dw_mmc: Add Synopsys DesignWare mmc host driver.' \
/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
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).