From: Takashi Iwai <tiwai@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: Allow ALSA input jacks to be accessed by the current user
Date: Fri, 17 Jun 2011 12:51:53 +0000 [thread overview]
Message-ID: <s5htybo62om.wl%tiwai@suse.de> (raw)
In-Reply-To: <4DFA0F40.7000204@canonical.com>
At Fri, 17 Jun 2011 14:45:52 +0200,
Lennart Poettering wrote:
>
> On Fri, 17.06.11 14:42, Takashi Iwai (tiwai@suse.de) wrote:
>
> > > If you have the patches ready to convert all drivers which currently can
> > > do jack sensing over to the new scheme with control elements, then we
> > > should probably focus on that for the future, shouldn't we?
> >
> > For PA work, I suppose so (although I won't object to someone working
> > on the implementation with the present input-jack layer :)
> > But you can see David's patch basically independent from PA.
>
> Well, but I'd guess that the access permissions only really matter for
> PA, right?
Not really. For example, I was asked about the input-jack stuff by
a couple of vendors for their own products, apparently running without
PA.
> So if we say that proper jack sensing via control elements is
> the way to go, then PA should adopt this new scheme and this new scheme
> only, and not bother with the input device cruft, and the udev patch
> should not be merged either as PA would be its only consumer...
I would be against the patch if the change were too intrusive,
but this change itself looks small enough to me.
The question whether PA should use it or not is a different thing.
thanks,
Takashi
next prev parent reply other threads:[~2011-06-17 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 14:12 [PATCH] udev: Allow ALSA input jacks to be accessed by the current David Henningsson
2011-06-16 14:28 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Kay Sievers
2011-06-16 14:48 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-16 14:55 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Kay Sievers
2011-06-16 15:02 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-17 6:17 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current David Henningsson
2011-06-17 6:20 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-17 11:27 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current David Henningsson
2011-06-17 12:31 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Lennart Poettering
2011-06-17 12:42 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-17 12:45 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Lennart Poettering
2011-06-17 12:51 ` Takashi Iwai [this message]
2011-06-17 13:00 ` Lennart Poettering
2011-06-17 13:05 ` Kay Sievers
2011-06-17 13:10 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the current user Takashi Iwai
2011-06-17 13:15 ` Takashi Iwai
2011-06-17 13:25 ` [PATCH] udev: Allow ALSA input jacks to be accessed by the Kay Sievers
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=s5htybo62om.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-hotplug@vger.kernel.org \
/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).