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: Tue, 24 Feb 2009 18:46:14 +0000 [thread overview]
Message-ID: <20090224184612.GA7121@sirena.org.uk> (raw)
In-Reply-To: <2C7D3DF36ADFFC479B44490D912B616705EC8B10D0@dlee07.ent.ti.com>
On Tue, Feb 24, 2009 at 11:37:47AM -0600, Lopez Cruz, Misael wrote:
> About adding GPIO functionality to jack detection, if the right
> place to request GPIOs and set its data direction is in board files
> (arch/*/mach-*/board-*.c), then there won't be much to do in jack
> code, only the irq request. Unless we move request and data direction
> setting to jack detection layer.
No, do that in the jack code. The board code should only be doing
things like putting the pins into GPIO mode (if that's not the default)
and any other steps required to ensure that they don't do anything like
consume a lot of power without the audio driver loaded.
prev parent reply other threads:[~2009-02-24 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2C7D3DF36ADFFC479B44490D912B616705D6329B7D@dlee07.ent.ti.com>
[not found] ` <200902202112.23307.david-b@pacbell.net>
[not found] ` <2C7D3DF36ADFFC479B44490D912B616705D61AF093@dlee07.ent.ti.com>
[not found] ` <200902222326.39232.david-b@pacbell.net>
2009-02-23 22:11 ` Configuring a TWL GPIO pin as an interrupt Lopez Cruz, Misael
2009-02-23 22:20 ` Mark Brown
2009-02-24 17:37 ` Lopez Cruz, Misael
2009-02-24 18:46 ` Mark Brown [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=20090224184612.GA7121@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox