All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [RFC PATCH] ALSA: hda: call ext hda codec link up/down if available
Date: Thu, 4 Feb 2021 10:07:09 +0200 (EET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2102040959490.864696@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <20210204075821.1503539-1-kai.vehmanen@linux.intel.com>

Hi,

On Thu, 4 Feb 2021, Kai Vehmanen wrote:
> To support more fine-grained control of link power, this patch
> implements new helper functions for codec drivers to turn codec links
> up and down. The HDA common suspend/resume code is modified to use
> the new functions. This allows to fully reuse the driver code both
> for plain and extended HDA controllers.

Takashi and others, this patch is a follow-up to the earlier thread about 
hdac link management:
https://mailman.alsa-project.org/pipermail/alsa-devel/2021-January/179715.html

We have absolutely no calls from sound/pci/hda/ to hdaudio_ext.h before
this patch, so I'm wondering if this is the right approach to take. 

It does seem to be the natural path forward and mimics what was done in 
e.g. hdac_hdmi. But we want to keep reusing driver code for all HDA 
implementations, so adding hdac-ext support to codec drivers seem like the 
best path.

Br, Kai

  reply	other threads:[~2021-02-04  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04  7:58 [RFC PATCH] ALSA: hda: call ext hda codec link up/down if available Kai Vehmanen
2021-02-04  8:07 ` Kai Vehmanen [this message]
2021-02-04  9:14   ` Takashi Iwai
2021-02-04 10:42     ` Kai Vehmanen
2021-02-04 14:04       ` Takashi Iwai

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=alpine.DEB.2.22.394.2102040959490.864696@eliteleevi.tm.intel.com \
    --to=kai.vehmanen@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ranjani.sridharan@linux.intel.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.