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: alsa-devel@alsa-project.org, broonie@kernel.org,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Rander Wang <rander.wang@intel.com>
Subject: Re: [PATCH] ALSA: hda: clarify comments on SCF changes
Date: Tue, 01 Nov 2022 11:51:13 +0100	[thread overview]
Message-ID: <87sfj36j8e.wl-tiwai@suse.de> (raw)
In-Reply-To: <20221031195505.249929-1-pierre-louis.bossart@linux.intel.com>

On Mon, 31 Oct 2022 20:55:05 +0100,
Pierre-Louis Bossart wrote:
> 
> The commit 1f9d3d98694b1 ("ALSA: hda - set intel audio clock to a
> proper value") added a number of misleading comments.
> 
> There is no ability to detect if an SCF value was set or not, what the
> code does is prevent the use of the 6MHz audio clock represented by
> the value 0 in LCTL.SCF. Changing the SCF settings does require the
> link to be power-cycled, but in all other cases the link is powered
> automatically when exiting reset. In other words, the power-cycle is
> an exception to the rule that the HDaudio legacy driver does not need
> to program SPA/CPA bits.
> 
> In addition, the SCF related changes are only relevant for the first
> link.
> 
> No functionality change, only comment clarifications.
> 
> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
> Reviewed-by: Rander Wang <rander.wang@intel.com>

Thanks, applied.


Takashi

      reply	other threads:[~2022-11-01 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 19:55 [PATCH] ALSA: hda: clarify comments on SCF changes Pierre-Louis Bossart
2022-11-01 10:51 ` Takashi Iwai [this message]

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=87sfj36j8e.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rander.wang@intel.com \
    --cc=ranjani.sridharan@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.