All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: "Ingo Brückl" <ib@wupperonline.de>, alsa-devel@alsa-project.org
Cc: tiwai@suse.de, superquad.vortex2@gmail.com
Subject: Re: [PATCH] ALSA: hda - Make path_has_mixer() tristate
Date: Fri, 06 Mar 2015 11:20:22 +0100	[thread overview]
Message-ID: <54F97F66.3040500@canonical.com> (raw)
In-Reply-To: <54f97b6b.2b113d67.bm000@wupperonline.de>



On 2015-03-06 10:57, Ingo Brückl wrote:
> Takashi Iwai wrote on Fri, 06 Mar 2015 10:38:49 +0100:
>
>> Even if you try parsing the topology at first with ignoring 0x15,
>> you'll need to add the path over 0x15 manually back to the
>> information.  Otherwise it can't work.
>
> Why can't it work? I'm not going to use the speaker.

There is no known hardware that has an speaker with no connection to it 
(and it would be a BIOS error if there was one), so it is not a priority 
(perhaps not even of interest) of the driver to support it.
Especially not as the option of using e g hdajackretask [1] to disable 
the speaker permanently is an easier and better way than starting to 
mess around with the connections and paths manually.

I understand that your intentions are good and that you want to help 
other users as well, and I don't want to scare you off, but in this case 
it seems to me like you have some private patches that makes the driver 
half broken, and then you want the official Linux kernel to fix up your 
private half broken scenario. Which doesn't really make sense.

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

[1] or the kernel interfaces that hdajackretask is a front-end for

  reply	other threads:[~2015-03-06 10:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 11:20 [PATCH] ALSA: hda - Make path_has_mixer() tristate Ingo Brückl
2015-03-04 11:48 ` Takashi Iwai
2015-03-05 10:20   ` Ingo Brückl
2015-03-05 11:38     ` Takashi Iwai
2015-03-05 16:44       ` Ingo Brückl
2015-03-06  9:38         ` Takashi Iwai
2015-03-06  9:57           ` Ingo Brückl
2015-03-06 10:20             ` David Henningsson [this message]
2015-03-06 10:45               ` Ingo Brückl
2015-03-06 10:54               ` Takashi Iwai
2015-03-06 11:07                 ` Ingo Brückl
2015-03-06 11:33                   ` Takashi Iwai
2015-03-06 12:33                     ` Ingo Brückl
2015-03-06 13:13                       ` Takashi Iwai
2015-03-04 14:08 ` Raymond Yau

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=54F97F66.3040500@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ib@wupperonline.de \
    --cc=superquad.vortex2@gmail.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.