alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 2/2] ALSA: Integrate control based jack reporting with core jack reporting
Date: Thu, 16 Feb 2012 19:59:09 +0000	[thread overview]
Message-ID: <20120216195908.GA32497@sirena.org.uk> (raw)
In-Reply-To: <CAN8cciaa4Htu5cS7AGuX347xY_Vbx5Uk9i4f605MRVmTQthtmw@mail.gmail.com>

On Tue, Feb 14, 2012 at 09:29:27AM +0800, Raymond Yau wrote:

I really shouldn't have ot remind you to not remove people from the CC
list, this is really basic stuff...

> 1) The problem of core jack api which is tailor made for embedded
> device, it assume there is only one sound card

This is not the case at all, there is no such assumption and indeed many
embedded devices have multiple sound cards.

> when the desktop computer have more than one sound cards which have jack detect
> there is no mapping to which sound card has the events.

The jack device is a child of the sound card, userspace can look at the
parent to see which sound card a given jack is associated with.

> 2) if the objective of adding jack detection is for trapping
> plug/unplug event to trigger the reconfiguration of audio server

> http://thread.gmane.org/gmane.linux.alsa.devel/89781/focus=89788

> does the audio server require to know the initial state of the hdmi
> or just need the trigger event ?

For all three of the accessory detection mechanisms the state can be
read at any time.

  reply	other threads:[~2012-02-16 19:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 19:48 [PATCH 1/2] ALSA: Use a define for the number of jack switch types Mark Brown
2012-02-07 19:48 ` [PATCH 2/2] ALSA: Integrate control based jack reporting with core jack reporting Mark Brown
2012-02-08  8:36   ` David Henningsson
2012-02-08 11:46     ` Mark Brown
2012-02-08 13:35       ` David Henningsson
2012-02-08 13:57         ` Mark Brown
2012-02-10 10:55         ` Takashi Iwai
2012-02-10 11:36           ` Mark Brown
2012-02-10 12:16             ` Takashi Iwai
2012-02-10 13:08           ` David Henningsson
2012-02-10 15:50             ` Mark Brown
2012-02-10 16:09               ` David Henningsson
2012-02-10 16:39                 ` Mark Brown
2012-02-13 13:56                   ` Takashi Iwai
2012-02-13 15:44                     ` Mark Brown
2012-02-13 17:40                       ` Takashi Iwai
2012-02-13 19:23                         ` Mark Brown
2012-02-14  7:20                         ` David Henningsson
2012-02-15  2:04                           ` Mark Brown
2012-02-22 16:52                           ` Takashi Iwai
2012-02-22 17:18                             ` Mark Brown
2012-02-22 17:34                               ` Takashi Iwai
2012-02-22 18:54                                 ` Mark Brown
2012-02-22 20:35                                   ` Takashi Iwai
2012-02-22 20:55                                     ` Mark Brown
2012-02-23  8:10                                       ` Takashi Iwai
2012-02-23  7:25                             ` David Henningsson
2012-02-14  1:29           ` Raymond Yau
2012-02-16 19:59             ` Mark Brown [this message]
2012-02-22 15:02 ` [PATCH 1/2] ALSA: Use a define for the number of jack switch types Mark Brown
2012-02-22 16:28   ` Takashi Iwai
2012-02-22 16:34     ` Mark Brown
2012-02-22 16:41       ` Takashi Iwai
2012-02-27 16:37         ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2012-03-01 17:48 [PATCH 2/2] ALSA: Integrate control based jack reporting with core jack reporting Takashi Iwai
2012-03-02  6:26 ` David Henningsson
2012-03-02  7:16   ` Takashi Iwai
2012-03-02 11:45     ` 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=20120216195908.GA32497@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=superquad.vortex2@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;
as well as URLs for NNTP newsgroup(s).