All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Harsha Priya <harshapriya.n@intel.com>,
	kai.vehmanen@intel.com, alsa-devel@alsa-project.org,
	Emmanuel Jillela <emmanuel.jillela@intel.com>
Subject: Re: [PATCH] ALSA: hda/hdmi: Add Intel silent stream support
Date: Wed, 24 Jun 2020 19:33:13 +0200	[thread overview]
Message-ID: <s5hftakid2e.wl-tiwai@suse.de> (raw)
In-Reply-To: <2404f45d-832d-69a0-fb3b-1981ae455f50@linux.intel.com>

On Wed, 24 Jun 2020 19:05:14 +0200,
Pierre-Louis Bossart wrote:
> 
> 
> 
> On 6/24/20 11:43 AM, Takashi Iwai wrote:
> > On Wed, 24 Jun 2020 17:33:45 +0200,
> > Pierre-Louis Bossart wrote:
> >>
> >>
> >>>>> The silent stream is enabled with a Kconfig option, as well as a kernel
> >>>>> parameter should there be a need to override the build time default.
> >>>>
> >>>> I'm not sure whether the module option is the best interface.
> >>>> An alternative is a mixer element that controls dynamically.  Then
> >>>> it'll be per card unlike the module option.
> >>>
> >>> +1, kcontrol seems the appropriate way to control this.
> >>
> >> It was my suggestion to use Kconfig+kernel parameter for
> >> simplicity/overrides.
> >>
> >> The kcontrol is a nice idea, but in practice we typically only have
> >> one card dealing with HDMI.
> >
> > Not really.  There are systems with two HDMI outputs from both
> > integrated and discrete GPUs.  Most modern systems are only with
> > hybrid graphics, though.
> 
> Ok, maybe I am mistaken, in most of the HDMI issues we've seen only
> one HDMI source.
> 
> But it's a good point that this is only supposed to be used for Intel
> whether it's a kernel parameter or a kcontrol shouldn't this be
> dependent on a PCI ID being detected and a SKYLAKE flag being set?
> it's my understanding that this applies from Skylake to TigerLake, not
> before.

I guess we can check it from the codec ID?  Change the probe function
for Skylake+ codecs to patch_i915_skl_hdmi and co, and set the flag
there.

> >> It also doesn't have a UCM representation
> >> so would force the use of amixer and manual configs, or the UCM file
> >> would always set the mode.
> >
> > But people usually use the distro kernels, so the situation is more or
> > less equivalent; you'd have to adjust a module option manually if you
> > want a different one from the default, and you'd have to be root to
> > change it.
> >
> > So, rather the question is how we should provide the setup of such
> > parameter.  It's supposed to be a part of power management stuff that
> > should be touched by either a smart PM tool or a manual override such
> > as runtime PM setup?  Or can it be seen as a more casual tuning?
> 
> I am not aware of such tools. The only thing I know is that some of
> the HDaudio power settings are already controlled by kernel
> parameters, e.g.
> 
> /etc/modprobe.d/audio_powersave.conf
> options snd_hda_intel power_save=1

Yes, it's been the primary knob for years to turn on/off the runtime
PM for HD-audio and other legacy drivers.  This was used by powertop
or some other power-aware daemons and tools, to be toggled dynamically
per the power cable state or such.

And, how the silent stream feature should be seen?
Should it be a system-wide root-only setup or adjustable per user?
Would it be changed often?  Such questions and answers will lead us to
the right direction, I hope.


Takashi

  reply	other threads:[~2020-06-24 17:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 23:26 [PATCH] ALSA: hda/hdmi: Add Intel silent stream support Harsha Priya
2020-06-24  0:25 ` kernel test robot
2020-06-24  0:25   ` kernel test robot
2020-06-24  0:28 ` Pierre-Louis Bossart
2020-06-24  0:51   ` N, Harshapriya
2020-06-24  7:45 ` Takashi Iwai
2020-06-24  8:18   ` Jaroslav Kysela
2020-06-24 15:33     ` Pierre-Louis Bossart
2020-06-24 16:43       ` Takashi Iwai
2020-06-24 17:05         ` Pierre-Louis Bossart
2020-06-24 17:33           ` Takashi Iwai [this message]
2020-06-24 17:58             ` N, Harshapriya
2020-06-25  6:41               ` Takashi Iwai
2020-06-25  0:18             ` Arun Raghavan
2020-06-25  7:03               ` Takashi Iwai
2020-06-25 10:04                 ` [pulseaudio-discuss] " Tanu Kaskinen
2020-06-25 14:46                 ` Pierre-Louis Bossart
2020-06-25 15:30                   ` Jaroslav Kysela
2020-06-25 15:43                     ` Pierre-Louis Bossart
2020-06-24 17:21         ` Kai Vehmanen

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=s5hftakid2e.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=emmanuel.jillela@intel.com \
    --cc=harshapriya.n@intel.com \
    --cc=kai.vehmanen@intel.com \
    --cc=pierre-louis.bossart@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 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.