From: Mark Brown <broonie@kernel.org>
To: Christopher Freeman <cfreeman@nvidia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: jack: export gpio detect
Date: Fri, 11 Apr 2014 11:12:45 +0100 [thread overview]
Message-ID: <20140411101245.GO6518@sirena.org.uk> (raw)
In-Reply-To: <CF6C7514.3DC69%cfreeman@nvidia.com>
[-- Attachment #1.1: Type: text/plain, Size: 827 bytes --]
On Thu, Apr 10, 2014 at 04:24:58PM -0700, Christopher Freeman wrote:
> On 4/8/14 1:40 PM, "Christopher Freeman" <cfreeman@nvidia.com> wrote:
> >Mark, do you have a suggestion on how to plumb this up? The way I see it,
> >the machine drivers own the context for the gpios and soc-jack acts as a
> >helper library. I don't see a way to do this from the core.
> Any thoughts? One idea would be to change things such that jacks are
> registered with the core and the core is then allowed access to the gpio
> detect functionŠ This would make things common, but we're still opening
> up a function in the jack code. I don't see another way. (using the
> existing interface, we could free and add gpios on suspend/resumeŠ :-P)
Please allow a reasonable time for replies, especially during the merge
window.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-04-11 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 22:03 [PATCH] ASoC: jack: export gpio detect cfreeman
2014-04-03 22:07 ` Mark Brown
2014-04-08 20:40 ` Christopher Freeman
2014-04-10 23:24 ` Christopher Freeman
2014-04-11 10:12 ` Mark Brown [this message]
2014-04-14 19:55 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2014-03-26 21:38 cfreeman
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=20140411101245.GO6518@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cfreeman@nvidia.com \
--cc=lgirdwood@gmail.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