From: Mark Brown <broonie@sirena.org.uk>
To: "Lopez Cruz, Misael" <x0052729@ti.com>
Cc: David Brownell <david-b@pacbell.net>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Configuring a TWL GPIO pin as an interrupt
Date: Mon, 23 Feb 2009 22:20:16 +0000 [thread overview]
Message-ID: <20090223222016.GA6584@sirena.org.uk> (raw)
In-Reply-To: <2C7D3DF36ADFFC479B44490D912B616705D632A0EE@dlee07.ent.ti.com>
On Mon, Feb 23, 2009 at 04:11:04PM -0600, Lopez Cruz, Misael wrote:
[Please fix your mail client to wrap lines at ~80 characters, it makes
your mails much easier to work with.]
> I think that if I move the platform_device registration from machine
> driver to board file I can append jack detection information (gpio
> pin, irq) through "platform_data" of "dev" field in platform_device
> structure. And then in the "probe" part in ASoC machine driver I can
> receive it.
Yes, though unless you actually have a generic ASoC machine driver that
works over multiple boards it's as well just skipping the platform data.
Look at s3c24xx_uda134x for an example of doing this.
If these are CPU side GPIOs that you're talking about you'll also want
to write the standard utility for using gpiolib for jack detection that
I've not got round to doing yet :)
next prev parent reply other threads:[~2009-02-23 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 2:27 Configuring a TWL GPIO pin as an interrupt Lopez Cruz, Misael
2009-02-21 2:39 ` Felipe Balbi
2009-02-21 5:12 ` David Brownell
2009-02-23 6:07 ` Lopez Cruz, Misael
2009-02-23 7:26 ` David Brownell
2009-02-23 22:11 ` Lopez Cruz, Misael
2009-02-23 22:20 ` Mark Brown [this message]
2009-02-24 17:37 ` Lopez Cruz, Misael
2009-02-24 18:46 ` Mark Brown
2009-02-23 14:17 ` Mark Brown
2009-02-21 10:33 ` Koen Kooi
2009-02-22 20:35 ` Mark Brown
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=20090223222016.GA6584@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=x0052729@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.