public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap@vger.kernel.org
Subject: Re: (non-hs)mmc vs lockdep
Date: Thu, 20 Nov 2008 21:10:09 +0200	[thread overview]
Message-ID: <20081120191008.GG31944@frodo> (raw)
In-Reply-To: <200811201056.28399.david-b@pacbell.net>

On Thu, Nov 20, 2008 at 10:56:28AM -0800, David Brownell wrote:
> On Thursday 20 November 2008, Felipe Balbi wrote:
> > > >  TI OMAP MMC INTERFACE DRIVER
> > > >  P:     Carlos Aguiar, Anderson Briglia and Syed Khasim
> > > >  M:     linux-omap@vger.kernel.org
> > > 
> > > 
> > > Yeah sure. Let's also add maintainers for omap subsystems that have
> > > maintainers while we're at it.
> > 
> > sounds good. At least mmc is already there.
> 
> So, who's going to fix the bug with the non-highspeed MMC controller
> driver whereby it breaks with LOCKDEP enabled?
> 
> The "BUG_ON(irqs_disabled());" in mmc_omap_start_request() triggers,
> since something inside the latest ARM MM code assumes it's never called
> with IRQs blocked ... a regression was introduced at some point.  The
> same failure is seen in some other MMC controller drivers.

Well, I haven't seen patches from none of the three maintainers for
quite a while. Maybe someone at TI could take over the driver(s) ??

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-11-20 19:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ef0d8a250811200202o5852dabct8c5b135b86141f67@mail.gmail.com>
2008-11-20 10:55 ` TWL4030 asoc kcontrols and widgets Felipe Balbi
2008-11-20 17:32   ` Tony Lindgren
2008-11-20 17:42     ` Felipe Balbi
2008-11-20 18:56       ` (non-hs)mmc vs lockdep David Brownell
2008-11-20 19:10         ` Felipe Balbi [this message]

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=20081120191008.GG31944@frodo \
    --to=me@felipebalbi.com \
    --cc=david-b@pacbell.net \
    --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