All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@sirena.org.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	Matthew Ranostay <mranostay@embeddedalley.com>
Subject: Re: [PATCH] hda: add support for jack detection on IDT/Sigmatel
Date: Wed, 15 Oct 2008 16:32:53 +0100	[thread overview]
Message-ID: <20081015153251.GD14068@sirena.org.uk> (raw)
In-Reply-To: <s5hvdvtzytl.wl%tiwai@suse.de>

On Wed, Oct 15, 2008 at 05:02:14PM +0200, Takashi Iwai wrote:
> Matthew Ranostay wrote:

> > +	jack->input_dev->phys = "ALSA Jack Detection";

> Any reason to change?

Not like that.  The only reason it's set at all at the minute is because
evdev prints it out for diagnostic purposes and it'd show up as "(NULL)"
which sets off alarm bells for people.  The particular string isn't
really important and the terseness varies between drivers that use fixed
strings.

Note that this isn't the device name - that should generally be verbose
(and is currently the card longname plus jack name which is idiomatic
for this).

> Well, I think even the original phys value "ALSA" is a bit strange in
> comparison with values of other input drivers, such as
> "isa0060/serio0/input0", "PNP0C0C/button/input0", too...
> Mark, what do you think?

It should ideally be something based off the location of the card in the
system (like those you quote above) - the idea is that it's something
that doesn't change between reboots and identifies the device.  Not all
input devices put something meaningful there.  If we change it to
anything it should probably be to something based off the bus_id of the
input device.

It mostly only comes into play if you've got more than one of a device
in the system and even then AIUI user space just uses sysfs these days,
which is why I didn't bother originally.

  parent reply	other threads:[~2008-10-15 15:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 14:43 [PATCH] hda: add support for jack detection on IDT/Sigmatel Matthew Ranostay
2008-10-15 15:02 ` Takashi Iwai
2008-10-15 15:19   ` Matthew Ranostay
2008-10-15 15:35     ` Takashi Iwai
2008-10-15 15:32   ` Mark Brown [this message]
2008-10-15 15:44 ` Mark Brown
2008-10-15 15:45   ` Matthew Ranostay
2008-10-15 15:47   ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2008-10-15 18:45 Matthew Ranostay
2008-10-16  6:54 ` Takashi Iwai

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=20081015153251.GD14068@sirena.org.uk \
    --to=broonie@sirena.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=mranostay@embeddedalley.com \
    --cc=tiwai@suse.de \
    /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.