From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap@vger.kernel.org, Balaji T K <balajitk@ti.com>,
"Venkatraman S." <svenkatr@ti.com>
Subject: Re: Panda: USB crash with today's linux-next
Date: Mon, 14 May 2012 11:14:14 -0700 [thread overview]
Message-ID: <20120514181413.GA17852@atomide.com> (raw)
In-Reply-To: <20120514175838.GA31200@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti.com> [120514 11:04]:
>
> That whole MMC card detection is also pretty screwed up. Balaji/Venkat,
> can you guys look into that ? Probably making something generic using a
> threaded IRQ handler ?
>
> I mean, all the MMC core should need is an IRQ number (through GPIOs or
> not doesn't/shouldn't matter) and it should be able to use a threaded
> IRQ handler to kick the card detection/initialization.
That's mostly done.. Just need to update the patches for it.
I posted some patches to take care of the card detection in the MMC
driver by leaving out the platform callbacks:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-March/087303.html
That's using gpiochip_find_by_name(), but after talking with Grant
about that, we agreed gpiochip_find_by_name() should be local as there's
no guarantees about anything with the gpiochip names.
Regards,
Tony
next prev parent reply other threads:[~2012-05-14 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1336996151.2333.3.camel@deskari>
2012-05-14 12:15 ` Panda: USB crash with today's linux-next Felipe Balbi
2012-05-14 12:24 ` Tomi Valkeinen
2012-05-14 12:29 ` Felipe Balbi
2012-05-14 12:47 ` Felipe Balbi
2012-05-14 17:06 ` Cousson, Benoit
2012-05-14 17:58 ` Felipe Balbi
2012-05-14 18:14 ` Tony Lindgren [this message]
2012-05-14 18:37 ` Tony Lindgren
2012-05-14 19:35 ` Felipe Balbi
2012-05-15 20:14 ` Tony Lindgren
2012-05-16 8:39 ` Felipe Balbi
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=20120514181413.GA17852@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=balajitk@ti.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=svenkatr@ti.com \
--cc=tomi.valkeinen@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