From: Ben Dooks <ben-linux@fluff.org>
To: Ben Dooks <ben@fluff.org>
Cc: Cory Maccarrone <darkstar6262@gmail.com>,
linux-mmc@vger.kernel.org, akpm@linux-foundation.org,
Ladislav Michl <ladis@linux-mips.org>,
linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
Marek Belisko <marek.belisko@open-nandra.com>
Subject: Re: [PATCH] mmc-omap: Add support for 16-bit and 32-bit registers
Date: Mon, 8 Mar 2010 10:04:14 +0000 [thread overview]
Message-ID: <20100308100414.GV10014@trinity.fluff.org> (raw)
In-Reply-To: <20100307225901.GU10014@trinity.fluff.org>
On Sun, Mar 07, 2010 at 10:59:01PM +0000, Ben Dooks wrote:
> On Sun, Mar 07, 2010 at 09:47:58AM -0800, Cory Maccarrone wrote:
> > From: Marek Belisko <marek.belisko@open-nandra.com>
> >
> > 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 resolve
> > this, a bit shift is performed on base register addresses, either by 1 or 2
> > bits depending on the CPU in use. This yields the correct registers for
> > each CPU.
>
> merged the previous one into my tree earlier today.
ignore this, didn't read the message properly and thought it was the i2c
patch.
> > Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com>
> > Signed-off-by: Cory Maccarrone <darkstar6262@gmail.com>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
> > ---
> > drivers/mmc/host/omap.c | 62 +++++++++++++++++++++++++----------------------
> > 1 files changed, 33 insertions(+), 29 deletions(-)
> >
> > This is a resubmit of a patch I sent in several months ago. Tony Lindgren merged
> > this into linux-omap's master and testing branches but has stated that he will not
> > merge it further as linux-mmc needs to approve this. There hasn't been any comments
> > raised on either of the linux-omap or linux-mmc mailing lists about problems. Due to
> > the unique nature of the omap7xx platform, this patch is required for MMC card access.
> > Is there any chance this can be included into the next -rc cycle, as it is a fix for
> > devices that have 16-bit registers?
> >
> > diff --git a/drivers/mmc/host/omap.c b/drivers/mmc/host/omap.c
> > index c6d7e8e..53362c4 100644
> > --- a/drivers/mmc/host/omap.c
> > +++ b/drivers/mmc/host/omap.c
> > @@ -38,30 +38,30 @@
> > #include <plat/fpga.h>
> >
> > #define OMAP_MMC_REG_CMD 0x00
> > -#define OMAP_MMC_REG_ARGL 0x04
> > -#define OMAP_MMC_REG_ARGH 0x08
> > -#define OMAP_MMC_REG_CON 0x0c
> > -#define OMAP_MMC_REG_STAT 0x10
> > -#define OMAP_MMC_REG_IE 0x14
> > -#define OMAP_MMC_REG_CTO 0x18
> > -#define OMAP_MMC_REG_DTO 0x1c
> > -#define OMAP_MMC_REG_DATA 0x20
> > -#define OMAP_MMC_REG_BLEN 0x24
> > -#define OMAP_MMC_REG_NBLK 0x28
> > -#define OMAP_MMC_REG_BUF 0x2c
> > -#define OMAP_MMC_REG_SDIO 0x34
> > -#define OMAP_MMC_REG_REV 0x3c
> > -#define OMAP_MMC_REG_RSP0 0x40
> > -#define OMAP_MMC_REG_RSP1 0x44
> > -#define OMAP_MMC_REG_RSP2 0x48
> > -#define OMAP_MMC_REG_RSP3 0x4c
> > -#define OMAP_MMC_REG_RSP4 0x50
> > -#define OMAP_MMC_REG_RSP5 0x54
> > -#define OMAP_MMC_REG_RSP6 0x58
> > -#define OMAP_MMC_REG_RSP7 0x5c
> > -#define OMAP_MMC_REG_IOSR 0x60
> > -#define OMAP_MMC_REG_SYSC 0x64
> > -#define OMAP_MMC_REG_SYSS 0x68
> > +#define OMAP_MMC_REG_ARGL 0x01
> > +#define OMAP_MMC_REG_ARGH 0x02
> > +#define OMAP_MMC_REG_CON 0x03
> > +#define OMAP_MMC_REG_STAT 0x04
> > +#define OMAP_MMC_REG_IE 0x05
> > +#define OMAP_MMC_REG_CTO 0x06
> > +#define OMAP_MMC_REG_DTO 0x07
> > +#define OMAP_MMC_REG_DATA 0x08
> > +#define OMAP_MMC_REG_BLEN 0x09
> > +#define OMAP_MMC_REG_NBLK 0x0a
> > +#define OMAP_MMC_REG_BUF 0x0b
> > +#define OMAP_MMC_REG_SDIO 0x0d
> > +#define OMAP_MMC_REG_REV 0x0f
> > +#define OMAP_MMC_REG_RSP0 0x10
> > +#define OMAP_MMC_REG_RSP1 0x11
> > +#define OMAP_MMC_REG_RSP2 0x12
> > +#define OMAP_MMC_REG_RSP3 0x13
> > +#define OMAP_MMC_REG_RSP4 0x14
> > +#define OMAP_MMC_REG_RSP5 0x15
> > +#define OMAP_MMC_REG_RSP6 0x16
> > +#define OMAP_MMC_REG_RSP7 0x17
> > +#define OMAP_MMC_REG_IOSR 0x18
> > +#define OMAP_MMC_REG_SYSC 0x19
> > +#define OMAP_MMC_REG_SYSS 0x1a
> >
> > #define OMAP_MMC_STAT_CARD_ERR (1 << 14)
> > #define OMAP_MMC_STAT_CARD_IRQ (1 << 13)
> > @@ -77,8 +77,9 @@
> > #define OMAP_MMC_STAT_CARD_BUSY (1 << 2)
> > #define OMAP_MMC_STAT_END_OF_CMD (1 << 0)
> >
> > -#define OMAP_MMC_READ(host, reg) __raw_readw((host)->virt_base + OMAP_MMC_REG_##reg)
> > -#define OMAP_MMC_WRITE(host, reg, val) __raw_writew((val), (host)->virt_base + OMAP_MMC_REG_##reg)
> > +#define OMAP_MMC_REG(host, reg) (OMAP_MMC_REG_##reg << (host)->reg_shift)
> > +#define OMAP_MMC_READ(host, reg) __raw_readw((host)->virt_base + OMAP_MMC_REG(host, reg))
> > +#define OMAP_MMC_WRITE(host, reg, val) __raw_writew((val), (host)->virt_base + OMAP_MMC_REG(host, reg))
> >
> > /*
> > * Command types
> > @@ -132,6 +133,7 @@ struct mmc_omap_host {
> > int irq;
> > unsigned char bus_mode;
> > unsigned char hw_bus_mode;
> > + unsigned int reg_shift;
> >
> > struct work_struct cmd_abort_work;
> > unsigned abort:1;
> > @@ -679,9 +681,9 @@ mmc_omap_xfer_data(struct mmc_omap_host *host, int write)
> > host->data->bytes_xfered += n;
> >
> > if (write) {
> > - __raw_writesw(host->virt_base + OMAP_MMC_REG_DATA, host->buffer, n);
> > + __raw_writesw(host->virt_base + OMAP_MMC_REG(host, DATA), host->buffer, n);
> > } else {
> > - __raw_readsw(host->virt_base + OMAP_MMC_REG_DATA, host->buffer, n);
> > + __raw_readsw(host->virt_base + OMAP_MMC_REG(host, DATA), host->buffer, n);
> > }
> > }
> >
> > @@ -899,7 +901,7 @@ mmc_omap_prepare_dma(struct mmc_omap_host *host, struct mmc_data *data)
> > int dst_port = 0;
> > int sync_dev = 0;
> >
> > - data_addr = host->phys_base + OMAP_MMC_REG_DATA;
> > + data_addr = host->phys_base + OMAP_MMC_REG(host, DATA);
> > frame = data->blksz;
> > count = sg_dma_len(sg);
> >
> > @@ -1492,6 +1494,8 @@ static int __init mmc_omap_probe(struct platform_device *pdev)
> > }
> > }
> >
> > + host->reg_shift = (cpu_is_omap7xx() ? 1 : 2);
> > +
> > return 0;
> >
> > err_plat_cleanup:
> > --
> > 1.6.3.3
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> --
> Ben
>
> Q: What's a light-year?
> A: One-third less calories than a regular year.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-03-08 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 17:47 [PATCH] mmc-omap: Add support for 16-bit and 32-bit registers Cory Maccarrone
2010-03-07 22:59 ` Ben Dooks
2010-03-08 0:16 ` Cory Maccarrone
2010-03-08 10:04 ` Ben Dooks [this message]
2010-05-13 19:29 ` Tony Lindgren
2010-05-13 19:41 ` Andrew Morton
2010-05-13 19:49 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2009-11-15 3:24 [PATCH] [mmc-omap] " Cory Maccarrone
2009-11-18 18:41 ` Ladislav Michl
2009-11-18 21:09 ` Cory Maccarrone
2009-11-18 23:35 ` Ladislav Michl
2009-10-03 21:57 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=20100308100414.GV10014@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=akpm@linux-foundation.org \
--cc=ben@fluff.org \
--cc=darkstar6262@gmail.com \
--cc=ladis@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=marek.belisko@open-nandra.com \
--cc=tony@atomide.com \
/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).