From: Ladislav Michl <Ladislav.Michl@seznam.cz>
To: Cory Maccarrone <darkstar6262@gmail.com>
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 19:41:55 +0100 [thread overview]
Message-ID: <20091118184152.GA6865@localhost.localdomain> (raw)
In-Reply-To: <1258255495.4209.3.camel@runt>
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...
> * 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.
> 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
Best regards,
ladis
next prev parent reply other threads:[~2009-11-18 18:41 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 [this message]
2009-11-18 21:09 ` Cory Maccarrone
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=20091118184152.GA6865@localhost.localdomain \
--to=ladislav.michl@seznam.cz \
--cc=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).