From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Harsha, Priya" <priya.harsha@intel.com>
Cc: "Koul, Vinod" <vinod.koul@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] [RFC 8/13] Intel SST sound card driver
Date: Tue, 7 Jul 2009 12:42:28 +0100 [thread overview]
Message-ID: <20090707114227.GD14393@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <98769532B4BB14429434178695419EAE5BBC230C@bgsmsx501.gar.corp.intel.com>
On Tue, Jul 07, 2009 at 12:05:45PM +0530, Harsha, Priya wrote:
> >-----Original Message-----
> >From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
> >ALSA core has an interface for representing jacks to user space which
> >should be used here - see include/sound/jack.h.
> Thanks for the note. I shall look into it further. Can you suggest any
> example ALSA driver that uses this functionality so that I can have a
A lot of the HDA drivers use it and there's a wrapper for ASoC too -
it's fairly likely that if you're running a current kernel your desktop
PC will support this interface already. Searching the kernel source for
snd_jack_new() should turn up everything there is at the minute.
> reference. Also quick question around this, can I use this jack.h to
> event the user space?
Yes, the jacks currently appear as input devices to applications.
Takashi was also considering adding some ALSA-specific ways of reading
the state to go alongside these.
next prev parent reply other threads:[~2009-07-07 11:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 7:06 [PATCH] [RFC 8/13] Intel SST sound card driver Vinod Koul
2009-07-03 15:16 ` Takashi Iwai
2009-07-07 6:20 ` Harsha, Priya
2009-07-07 6:49 ` Takashi Iwai
2009-07-07 7:04 ` Harsha, Priya
2009-07-07 7:11 ` Takashi Iwai
2009-07-07 7:16 ` Harsha, Priya
2009-07-07 7:26 ` Takashi Iwai
2009-07-08 5:44 ` Harsha, Priya
2009-07-04 10:57 ` Mark Brown
2009-07-07 6:35 ` Harsha, Priya
2009-07-07 11:42 ` Mark Brown [this message]
2009-07-08 5:44 ` Harsha, Priya
2009-07-08 9:46 ` Mark Brown
2009-07-17 7:01 ` Harsha, Priya
2009-07-17 10:18 ` Mark Brown
2009-08-01 3:15 ` Harsha, Priya
2009-08-01 9:46 ` Mark Brown
2009-08-03 7:15 ` Harsha, Priya
2009-08-03 10:12 ` Mark Brown
2009-08-03 11:44 ` Harsha, Priya
2009-08-03 11:53 ` Mark Brown
2009-08-10 16:23 ` Harsha, Priya
2009-08-10 16:34 ` Mark Brown
2009-08-11 10:43 ` Harsha, Priya
2009-08-11 10:47 ` Mark Brown
2009-09-09 12:07 ` control names Harsha, Priya
2009-09-09 12:11 ` Jaroslav Kysela
2009-09-09 12:15 ` Mark Brown
2009-09-09 12:23 ` Harsha, Priya
2009-09-09 12:35 ` Mark Brown
2009-09-11 7:04 ` Harsha, Priya
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=20090707114227.GD14393@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=priya.harsha@intel.com \
--cc=vinod.koul@intel.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.