public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <felipe.balbi@nokia.com>
Cc: Steve Sakoman <sakoman@gmail.com>,
	Koen Kooi <k.kooi@student.utwente.nl>,
	"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>
Subject: Re: MMC broken on beagleboard with current git
Date: Tue, 30 Sep 2008 16:35:51 +0300	[thread overview]
Message-ID: <20080930133550.GA15017@atomide.com> (raw)
In-Reply-To: <20080930132222.GC2492@gandalf.research.nokia.com>

* Felipe Balbi <felipe.balbi@nokia.com> [080930 16:22]:
> On Tue, Sep 30, 2008 at 03:58:39PM +0300, Tony Lindgren wrote:
> > + * One controller can have multiple slots, like on some omap boards using
> > + * omap.c controller driver. Luckily this is not currently done on any known
> > + * omap_hsmmc.c device.
> 
> this is only true for omap1 afaict.

Do you mean omap.c but not on omap_hsmmc.c?

If for sure we'll never have multiple slots on omap_hsmmc.c, we could simplify
the code and assume the slot is always 0.

Tony

  reply	other threads:[~2008-09-30 13:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-25  8:41 MMC broken on beagleboard with current git Koen Kooi
2008-09-25  8:51 ` Tony Lindgren
2008-09-25  9:23   ` Koen Kooi
2008-09-25  9:47     ` Tony Lindgren
2008-09-25 10:24       ` Koen Kooi
2008-09-25 10:39         ` Tony Lindgren
2008-09-25 15:24           ` Steve Sakoman
2008-09-26  7:42             ` Tony Lindgren
2008-09-26 11:13               ` Tony Lindgren
2008-09-28 12:46                 ` Tony Lindgren
2008-09-30 12:58                   ` Tony Lindgren
2008-09-30 13:22                     ` Felipe Balbi
2008-09-30 13:35                       ` Tony Lindgren [this message]
2008-09-30 13:43                         ` Felipe Balbi
2008-09-30 13:24                     ` Felipe Contreras

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=20080930133550.GA15017@atomide.com \
    --to=tony@atomide.com \
    --cc=felipe.balbi@nokia.com \
    --cc=k.kooi@student.utwente.nl \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakoman@gmail.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