LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Will Newton <will.newton@gmail.com>
To: Chris Ball <cjb@laptop.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org, Matt Fleming <matt@console-pimps.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dw_mmc: Add Synopsys DesignWare mmc host driver.
Date: Sun, 12 Dec 2010 14:03:52 +0000 [thread overview]
Message-ID: <AANLkTinMYeWNLu8e7xyBTvjmeFMsJ5sDGtsCesu04d4K@mail.gmail.com> (raw)
In-Reply-To: <20101212135224.GA31812@void.printf.net>
On Sun, Dec 12, 2010 at 1:52 PM, Chris Ball <cjb@laptop.org> wrote:
> Hi Will,
>
> On Sun, Dec 12, 2010 at 10:57:44AM +0000, Will Newton wrote:
>> > drivers/mmc/host/dw_mmc.c: In function ‘dw_mci_pull_data64’:
>> > drivers/mmc/host/dw_mmc.c:998: error: implicit declaration of function ‘__raw_readq’
>> >
>> > because arch/arm doesn't implement raw versions of these 64-bit accesses.
>> > I'm surprised that this driver hasn't been compiled on ARM before! What
>>
>> That particular bit of code has been added since it was last built for
>> arm. Our architecture can do 64bit accesses so we implement readq.
>> Unfortunately there doesn't seem to be a sane way to conditionalize
>> code for architectures that have or don't have readq, so I suspect
>> I'll have to just remove that branch of the if statement for now.
>
> (Russell, thanks for the excellent explanation.)
>
> Other drivers (MTD, gpio/basic_mmio_gpio.c, fs/fuse, pcm_oss.c)
> conditionalize uses of {read,write}q on BITS_PER_LONG >= 64, so
> something like this:
I don't think that's going to work, BITS_PER_LONG isn't equivalent to
"can do 64bit IO accesses", at least it isn't on our architecture. x86
is in the same situation it would appear, although x86 does explicitly
#define readq so it may be possible to #ifdef on that?
next prev parent reply other threads:[~2010-12-12 14:03 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 [this message]
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
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=AANLkTinMYeWNLu8e7xyBTvjmeFMsJ5sDGtsCesu04d4K@mail.gmail.com \
--to=will.newton@gmail.com \
--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 \
--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).