alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	wfg@linux.intel.com
Subject: Re: [PATCH] ALSA: HDA: Remove unconnected PCM devices for	Intel HDMI
Date: Tue, 23 Nov 2010 08:12:59 +0100	[thread overview]
Message-ID: <s5hy68kpl6s.wl%tiwai@suse.de> (raw)
In-Reply-To: <4CDD615A.7000807@canonical.com>

At Fri, 12 Nov 2010 16:46:34 +0100,
David Henningsson wrote:
> 
> Since I'm a little new in HDMI land and the patch is non-trivial, I 
> wouldn't mind some comments on this one. Also thanks to Jaroslav who 
> cleared a few things out about the logical and physical devices which 
> helped me figure out what I should do about it :-)
> 
> Anyway, here's the patch.
> 
> Some newer chips have more than one HDMI output, but usually not
> all of them are exposed as physical jacks. Removing the unused
> PCM devices (as indicated by BIOS in the pin config default) will
> reduce user confusion as they currently have to choose between
> several HDMI devices, some of them not working anyway.
> 
> Signed-off-by: David Henningsson <david.henningsson@canonical.com>

The patch looks mostly OK.
But this gives a few errors and warnings via checkpatch.pl.
Could you fix errors, at least?

Also some review comments:

>  static int hdmi_add_cvt(struct hda_codec *codec, hda_nid_t nid)
>  {
> +	int i;
>  	struct hdmi_spec *spec = codec->spec;
>  
> -	if (spec->num_cvts >= MAX_HDMI_CVTS) {
> -		snd_printk(KERN_WARNING
> -			   "HDMI: no space for converter %d\n", nid);
> +	for (i = 0; spec->pin_cvt[i] != nid; i++) 

I'd write with a normal loop like for (i = 0; i < spec->num_pins; i++)
This is easier to read.

> +		if (!spec->pin[i]) {
> +			snd_printd("HDMI: Skipping node %d (no connection)\n", nid);

Better to use snd_printdd().  snd_printd() is enabled on many distros,
and such an unnecessary kernel message may make user worry.

> @@ -951,17 +954,33 @@ static int hdmi_parse_codec(struct hda_codec *codec)
...
>  		case AC_WID_PIN:
>  			caps = snd_hda_param_read(codec, nid, AC_PAR_PIN_CAP);
>  			if (!(caps & (AC_PINCAP_HDMI | AC_PINCAP_DP)))
>  				continue;
> +
> +			config = snd_hda_codec_read(codec, nid, 0, 
> +					     AC_VERB_GET_CONFIG_DEFAULT, 0);
> +			if (((config & AC_DEFCFG_PORT_CONN) >> 
> +			    AC_DEFCFG_PORT_CONN_SHIFT) == AC_JACK_PORT_NONE)

You can use get_defcfg_connect() here.


thanks,

Takashi

  reply	other threads:[~2010-11-23  7:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 15:46 [PATCH] ALSA: HDA: Remove unconnected PCM devices for Intel HDMI David Henningsson
2010-11-23  7:12 ` Takashi Iwai [this message]
2010-11-23  9:29   ` David Henningsson
2010-11-23 11:06     ` Wu Fengguang
2010-11-23 13:51       ` Takashi Iwai
2010-11-23 14:19         ` David Henningsson
2010-11-23 14:58           ` Wu Fengguang
2010-11-24  9:39           ` Takashi Iwai
2010-11-23 15:15     ` Wu Fengguang
2010-11-23 15:40       ` David Henningsson
2010-11-23 15:54         ` Wu Fengguang
2010-11-24 13:50           ` David Henningsson
2010-11-23 16:16         ` Wu Fengguang
2010-12-07 19:10 ` Takashi Iwai
2012-02-01 12:38   ` RIDDICC

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=s5hy68kpl6s.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=wfg@linux.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 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).