From: Cory Maccarrone <darkstar6262@gmail.com>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: linux-mmc@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] [mmc-omap] Add support for 16-bit and 32-bit registers
Date: Wed, 18 Nov 2009 13:09:22 -0800 [thread overview]
Message-ID: <6cb013310911181309w6e21b8e9o62fad1a80f300c08@mail.gmail.com> (raw)
In-Reply-To: <20091118184152.GA6865@localhost.localdomain>
On Wed, Nov 18, 2009 at 10:41 AM, Ladislav Michl
<Ladislav.Michl@seznam.cz> wrote:
> On Sat, Nov 14, 2009 at 07:24:55PM -0800, Cory Maccarrone wrote:
>> The omap850 and omap730 use 16-bit registers instead of 32-bit, requiring
>> a modification of the register addresses in the mmc-omap driver. To
>> make this as portable as possible, I made the following changes:
>
> Hmm, I would not trade portability anyone currently needs for complexity...
Agreed, this solution is more complicated than it probably needs to be.
>
>> * Moved register address offsets from drivers/mmc/host/omap.c to
>> drivers/mmc/host/omap.h
>> * Implemented a lookup table for 16-bit and 32-bit register offsets
>> * Added a reg_size field in the mmc_omap_host structure
>> * Added code in mmc_omap_probe() to populate the reg_size
>> field based on processor in use
>> * Added inline function to return the register offset based on
>> the register size and register name
>> * Modified mmc-omap driver to use the new inline function to call out
>> register names
>
> All this could be probably done by making register definition an index and
> shifting it left by one or two depending on CPU. No lookup table needed.
Ah, good point, I hadn't considered that. I'll rework my
implementation to do that and resubmit.
>
>> This change should allow the omap7xx-series of processors to correctly
>> utilize the MMC driver.
>
> Did you test it? It does not work on 5910, see here:
> http://thread.gmane.org/gmane.linux.kernel.mmc/649
Not sure why it wouldn't work on the 5910. I tested it on my device,
and it works properly for me, but then I don't have an omap-based
device that uses 32-bit register definitions. I'm confused at the
post you have above though...Is that with my patch, or is that with
something else? It seems to reference the status of current git,
which I don't think this patch shouldn't be in.
- Cory
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-18 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 3:24 [PATCH] [mmc-omap] Add support for 16-bit and 32-bit registers Cory Maccarrone
2009-11-18 18:41 ` Ladislav Michl
2009-11-18 21:09 ` Cory Maccarrone [this message]
2009-11-18 23:35 ` Ladislav Michl
-- strict thread matches above, loose matches on Subject: below --
2010-03-07 17:47 [PATCH] mmc-omap: " Cory Maccarrone
2010-03-07 22:59 ` Ben Dooks
2010-03-08 0:16 ` Cory Maccarrone
2010-03-08 10:04 ` Ben Dooks
2010-05-13 19:29 ` Tony Lindgren
2010-05-13 19:41 ` Andrew Morton
2010-05-13 19:49 ` Tony Lindgren
2009-10-03 21:57 [PATCH] [mmc-omap] " Cory Maccarrone
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=6cb013310911181309w6e21b8e9o62fad1a80f300c08@mail.gmail.com \
--to=darkstar6262@gmail.com \
--cc=ladis@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.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).