From: David Brownell <david-b@pacbell.net>
To: Purushotam Kumar <purushotam@ti.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
linux-kernel@vger.kernel.org, drzeus-mmc@drzeus.cx
Subject: Re: [PATCH 1/1] DaVinci: MMC: Updated MMC/SD controller driver for DaVinci family.
Date: Mon, 23 Mar 2009 13:17:07 -0700 [thread overview]
Message-ID: <200903231317.07231.david-b@pacbell.net> (raw)
In-Reply-To: <1237378885-5918-1-git-send-email-purushotam@ti.com>
On Wednesday 18 March 2009, Purushotam Kumar wrote:
> From: Purshotam Kumar <purushotam@ti.com>
>
> This patch adds support for MMC/SD controller driver for DaVinci family SoC.
> This patch will work for SoC like DM6446 and DM355. SoC like DM365 and
> DA830 also has same controller with small variations and could supported/added
> easily by using this version of patch. It means that this version of patch
> could be used for all SoC which has been derived from DaVinci family.
>
> This patch has been generated against latest 2.6.29 mainline kernel. This patch
> will not compile currently because it depends notably on the EDMA utilities and
> chip/board setup, that will come at some point through the ARM tree. Please use
> currently DaVinci GIT tree for EDMA utilities and chip/board setup etc.
>
> Many thanks to David Brownell (david-b@pacbell.net) for his all support.
>
>
> Signed-off-by: Purshotam Kumar <purushotam@ti.com>
Sanity-tested against mainline with simple patches to add
EDMA and chip/board setup ... root-on-MMC works, just like
root-on-IDE.
Once you fix the build bug noted below:
Acked-by: David Brownell <dbrownell@users.sourceforge.net>
Though the PIO bits still bother me ... I'd use *only* the
io{read,write}8_rep() calls to load/unload the FIFO. While
those calls haven't broken yet, it's rude to (a) open-code
io{read,write}32_rep() like that, and (b) assume all buffers
coming in to that function are 32-bit aligned. PIO is hardly
ever used, given EDMA. Maybe just one or two calls when
enumerating. (SDIO might use it more often.) That can be
fixed a bit later.
Also, it'd be good to submit a patch to the DaVinci tree
to make it match whatever Pierre eventually merges. (Less
the clock name change, of course, which is only needed to
cope with the elderly clock logic now in mainline.)
> ---
> arch/arm/mach-davinci/include/mach/mmc.h | 25 +
> drivers/mmc/host/Kconfig | 8 +
> drivers/mmc/host/Makefile | 1 +
> drivers/mmc/host/davinci_mmc.c | 1257 ++++++++++++++++++++++++++++++
> 4 files changed, 1291 insertions(+), 0 deletions(-)
Build bug in probe():
> + host->clk = clk_get(&pdev->dev, MMCSDCLK);
Put quotes around "MMCSDCLK".
next prev parent reply other threads:[~2009-03-23 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 12:21 [PATCH 1/1] DaVinci: MMC: Updated MMC/SD controller driver for DaVinci family Purushotam Kumar
2009-03-23 20:17 ` David Brownell [this message]
2009-03-24 11:57 ` Kumar, Purushotam
2009-03-30 21:10 ` Andrew Morton
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=200903231317.07231.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=purushotam@ti.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