All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: "Hans J. Koch" <hjk@linutronix.de>
Cc: Daniel Mack <daniel@caiaq.de>,
	linux-arm-kernel@lists.infradead.org,
	John Ogness <jogness@linutronix.de>,
	linux-mmc@vger.kernel.org
Subject: Re: Is anyone working on SD/MMC driver for i.MX35 ?
Date: Fri, 2 Apr 2010 03:29:32 +0200	[thread overview]
Message-ID: <20100402012932.GE13989@pengutronix.de> (raw)
In-Reply-To: <20100401132234.GG2045@bluebox.local>

[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]

On Thu, Apr 01, 2010 at 03:22:35PM +0200, Hans J. Koch wrote:
> On Thu, Apr 01, 2010 at 03:20:17PM +0200, Daniel Mack wrote:
> > On Thu, Apr 01, 2010 at 02:57:40PM +0200, Hans J. Koch wrote:
> > > I need to get the MMC interface of an i.MX35 to work in the near future.
> > > To avoid duplicate work, I'd like to know if anybody already started
> > > work on this.
> > 
> > Is the controller very different from the one which is already supported
> > for MX31?
> 
> Yep. Completely different beast. Unfortunately.

(CCing linux-mmc)

And it is a mess, really :(

The kernel already has an esdhc-driver (and Anton already worked around a
number of hardware-bugs), but is tied into an of-driver because the core was
also used on PowerPC. There, it utilizes a 32-bit-byte-swaper which is not
needed on ARM. So, one has to rip all that out, generalize the sdhc-platform
support (possibly also abstract the quirk support) and make sure nothing
breaks.

I started and got MMC working, but it is by far not mainline quality (and maybe
bitrotten by now). Check the sdhci-pltfm branch at

http://git.pengutronix.de/?p=wsa/linux-2.6.git;a=summary

You see, there is still some of_* left in the platform-part.

Maybe you can push this a bit further,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: Is anyone working on SD/MMC driver for i.MX35 ?
Date: Fri, 2 Apr 2010 03:29:32 +0200	[thread overview]
Message-ID: <20100402012932.GE13989@pengutronix.de> (raw)
In-Reply-To: <20100401132234.GG2045@bluebox.local>

On Thu, Apr 01, 2010 at 03:22:35PM +0200, Hans J. Koch wrote:
> On Thu, Apr 01, 2010 at 03:20:17PM +0200, Daniel Mack wrote:
> > On Thu, Apr 01, 2010 at 02:57:40PM +0200, Hans J. Koch wrote:
> > > I need to get the MMC interface of an i.MX35 to work in the near future.
> > > To avoid duplicate work, I'd like to know if anybody already started
> > > work on this.
> > 
> > Is the controller very different from the one which is already supported
> > for MX31?
> 
> Yep. Completely different beast. Unfortunately.

(CCing linux-mmc)

And it is a mess, really :(

The kernel already has an esdhc-driver (and Anton already worked around a
number of hardware-bugs), but is tied into an of-driver because the core was
also used on PowerPC. There, it utilizes a 32-bit-byte-swaper which is not
needed on ARM. So, one has to rip all that out, generalize the sdhc-platform
support (possibly also abstract the quirk support) and make sure nothing
breaks.

I started and got MMC working, but it is by far not mainline quality (and maybe
bitrotten by now). Check the sdhci-pltfm branch at

http://git.pengutronix.de/?p=wsa/linux-2.6.git;a=summary

You see, there is still some of_* left in the platform-part.

Maybe you can push this a bit further,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100402/af49aabd/attachment.sig>

  reply	other threads:[~2010-04-02  1:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 12:57 Is anyone working on SD/MMC driver for i.MX35 ? Hans J. Koch
2010-04-01 13:20 ` Daniel Mack
2010-04-01 13:22   ` Hans J. Koch
2010-04-02  1:29     ` Wolfram Sang [this message]
2010-04-02  1:29       ` Wolfram Sang
2010-04-05 18:21       ` Anton Vorontsov
2010-04-05 18:21         ` Anton Vorontsov
2010-04-06  9:12         ` Hans J. Koch
2010-04-06  9:12           ` Hans J. Koch
2010-04-27 11:04           ` Wolfram Sang
2010-04-27 11:04             ` Wolfram Sang
2010-04-28 13:15             ` Hans J. Koch
2010-04-28 13:15               ` Hans J. Koch
2010-08-03 14:31               ` Wolfram Sang
2010-08-03 14:31                 ` Wolfram Sang
2010-08-05  9:44                 ` Hans J. Koch
2010-08-05  9:44                   ` Hans J. Koch
  -- strict thread matches above, loose matches on Subject: below --
2010-04-01 12:52 Hans J. Koch

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=20100402012932.GE13989@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=daniel@caiaq.de \
    --cc=hjk@linutronix.de \
    --cc=jogness@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.