From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <balbi@ti.com>, "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: Wed, 16 May 2012 11:39:35 +0300 [thread overview]
Message-ID: <20120516083934.GI17359@arwen.pp.htv.fi> (raw)
In-Reply-To: <20120515201426.GE17852@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]
On Tue, May 15, 2012 at 01:14:29PM -0700, Tony Lindgren wrote:
> * Felipe Balbi <balbi@ti.com> [120514 12:41]:
> > On Mon, May 14, 2012 at 11:37:43AM -0700, Tony Lindgren wrote:
> > > * Tony Lindgren <tony@atomide.com> [120514 11:19]:
> > > > * 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.
> > >
> > > Mostly done meaning "all the MMC core should need is an IRQ number"
> > > part that is :)
> >
> > but you've done it for omap_hsmmc.c, right ? What I meant is that the
> > whole card detection should be done at the MMC framework level.
>
> Yes what I did was just try to start gettting rid of the platform
> callbacks.
>
> > I mean, if we tell MMC core what's the card detect IRQ number, it should
> > be able to implement a generic version of omap_hsmmc_detect(). All that
> > thing does is read the current gpio status number and call
> > mmc_detect_change().
> >
> > mmc_detect_change() then kicks a delayed work, which shouldn't be needed
> > because omap_hsmmc_detect() (or the generic of it) is already using a
> > threaded IRQ.
>
> Yeah maybe it's doable.. The MMC driver needs to read the status of the
> card insert, but maybe that should be just just gpio_get_value().
>
> Then ideally the MMC driver would not have any knowledge how the GPIO
> is handled as it can come from whatever gpiochip using internal GPIO
> or TWL GPIO.
correct.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-05-16 8:41 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
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 [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=20120516083934.GI17359@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=b-cousson@ti.com \
--cc=balajitk@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=svenkatr@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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