From: "kishore kadiyala" <kishore.kadiyala@ti.com>
To: "Pakaravoor, Jagadeesh" <j-pakaravoor@ti.com>,
Tony Lindgren <tony@atomide.com>,
dbrownell@users.sourceforge.net
Cc: linux-omap@vger.kernel.org
Subject: Re: MMC not working on 3430SDP
Date: Tue, 3 Feb 2009 16:51:53 +0530 [thread overview]
Message-ID: <00a301c985f1$9e5bf910$LocalHost@wipultra796> (raw)
In-Reply-To: EAF47CD23C76F840A9E7FCE10091EFAB02A3D45333@dbde02.ent.ti.com
Hi ,
On 3430 SDP , the MMC card insertion and removal is not working on the
linux -omap tree !
It seems like interrupts are not getting triggered on Card insertion &
removal !
I wonder if it has to do something with GPIO library !
Also whether the GPIO library takes care of the requests to TWL4030 ?
Thanks & Regards,
Kishore
----- Original Message -----
From: "Pakaravoor, Jagadeesh" <j-pakaravoor@ti.com>
To: "Tony Lindgren" <tony@atomide.com>
Cc: <linux-omap@vger.kernel.org>
Sent: Tuesday, February 03, 2009 1:01 AM
Subject: OMAP: MMC not working on 3430SDP
> Hi,
> When using the latest Linux Omap code base, MMC functionality is broken.
> MMC card insertion is not giving interrupts. Also at proc/interrupts,
> where mmc interrupt should have been, the entry says:
> "Err: 0"
>
> --
> With Regards,
> Jagadeesh Bhaskar P
>
> ----------------------------
> Some men see things as they are and say why - I dream things that never
> were and say why not.
> - George Bernard Shaw
> ----------------------------
>
> --
> 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
>
>
next prev parent reply other threads:[~2009-02-03 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 19:31 OMAP: MMC not working on 3430SDP Pakaravoor, Jagadeesh
2009-02-03 11:21 ` kishore kadiyala
2009-02-03 11:31 ` Pillai, Manikandan
2009-02-03 11:21 ` kishore kadiyala [this message]
2009-02-03 12:44 ` Grazvydas Ignotas
2009-02-03 16:33 ` David Brownell
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='00a301c985f1$9e5bf910$LocalHost@wipultra796' \
--to=kishore.kadiyala@ti.com \
--cc=dbrownell@users.sourceforge.net \
--cc=j-pakaravoor@ti.com \
--cc=linux-omap@vger.kernel.org \
--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