All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Vinod Koul <vinod.koul@intel.com>, alsa-devel@alsa-project.org
Subject: Re: Changing snd_hda_intel.power_save default value ?
Date: Wed, 01 Nov 2017 17:54:53 +0100	[thread overview]
Message-ID: <s5ha806c52a.wl-tiwai@suse.de> (raw)
In-Reply-To: <9247bda8-da84-81e0-7897-8a45008c0d10@redhat.com>

On Wed, 01 Nov 2017 15:19:44 +0100,
Hans de Goede wrote:
> 
> Hi All,
> 
> I'm working on trying to improve the OOTB power-consumption
> of Linux (Fedora Workstation) on laptops.
> 
> One of the easy wins here is setting snd_hda_intel.power_save=1
> 
> I see that the default is configurable through a Kconfig option,
> currently Fedora is using the Kconfig default value of 0.
> 
> So I'm wondering if there any known issues with changing the
> default to 1 ?

This may bring click noises on some laptops or desktops, but it should
be OK for the functionalities.  On openSUSE Tumbleweed kernels, we
already pass 1 for some time.  Some reports came up occasionally but
they can work around by setting the module option.

> I was also thinking that maybe an automatic value
> (SND_HDA_POWER_SAVE_DEFAULT == -1) might be a good idea,
> which would mean 0 normally except for PCI-ids which are
> markes with a MOBILE flag in their driver_data in
> the azx_ids pci_device_id table ?

I'm afraid that it'd be hard to manage that table.  This is one of
mostly modified module option, e.g. a power-management daemon often
adjusts the value dynamically.
So, for modern distros, feel free simply set to value 1, but I see no
reason to hustle for changing kconfig default value in the tree.  For
the default value, we want to be conservative in general.


thanks,

Takashi

  reply	other threads:[~2017-11-01 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 14:19 Changing snd_hda_intel.power_save default value ? Hans de Goede
2017-11-01 16:54 ` Takashi Iwai [this message]
2017-11-01 18:11   ` Hans de Goede

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=s5ha806c52a.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=hdegoede@redhat.com \
    --cc=vinod.koul@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 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.