All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: songxiebing <songxiebing@kylinos.cn>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/intel: Synchronize the module parameter values of the power_save
Date: Mon, 02 Mar 2026 09:38:17 +0100	[thread overview]
Message-ID: <87v7femxs6.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260302081218.771520-1-songxiebing@kylinos.cn>

On Mon, 02 Mar 2026 09:12:18 +0100,
songxiebing wrote:
> 
> In set_default_power_save, if val is 0 and is not assigned to
> power_save, it leads to incorrect reading of the sys node, resulting in
> misjudgment, so modify it here.
> 
> Signed-off-by: songxiebing <songxiebing@kylinos.cn>

I'm afraid that this can break things in a subtle way, e.g. when there
are multiple HD-audio controllers, and only one of them is
blacklisted.

The power_save option is provided as a single knob for simplicity, in
the case if user wants to change intentionally.  And this doesn't
guaranteed to be the actual power-saving timeout value that could be
adjusted also via sysfs.


thanks,

Takashi

> ---
>  sound/hda/controllers/intel.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/sound/hda/controllers/intel.c b/sound/hda/controllers/intel.c
> index 3f434994c18d..6c6564396637 100644
> --- a/sound/hda/controllers/intel.c
> +++ b/sound/hda/controllers/intel.c
> @@ -2306,6 +2306,7 @@ static void set_default_power_save(struct azx *chip)
>  		dev_info(chip->card->dev, "Forcing power_save to 0 via option\n");
>  		val = 0;
>  	}
> +	power_save = val;
>  	snd_hda_set_power_save(&chip->bus, val * 1000);
>  }
>  
> -- 
> 2.25.1
> 

  reply	other threads:[~2026-03-02  8:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02  8:12 [PATCH] ALSA: hda/intel: Synchronize the module parameter values of the power_save songxiebing
2026-03-02  8:38 ` Takashi Iwai [this message]
2026-03-03  2:11 ` songxiebing
2026-03-05  4:19 ` kernel test robot
2026-03-05 14:52 ` kernel test robot

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=87v7femxs6.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=songxiebing@kylinos.cn \
    --cc=tiwai@suse.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 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.