From: Takashi Iwai <tiwai@suse.de>
To: Sameer Pujar <spujar@nvidia.com>
Cc: <tiwai@suse.com>, <perex@perex.cz>,
<kai.vehmanen@linux.intel.com>, <yang.jie@linux.intel.com>,
<pierre-louis.bossart@linux.intel.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH] ALSA: hda: avoid reset of sdo_limit
Date: Wed, 19 Aug 2020 16:53:17 +0200 [thread overview]
Message-ID: <s5hmu2qhele.wl-tiwai@suse.de> (raw)
In-Reply-To: <1597848273-25813-1-git-send-email-spujar@nvidia.com>
On Wed, 19 Aug 2020 16:44:33 +0200,
Sameer Pujar wrote:
>
> By default 'sdo_limit' is initialized with a default value of '8'
> as per spec. This is overridden in cases where a different value is
> required. However this is getting reset when snd_hdac_bus_init_chip()
> is called again, which happens during runtime PM cycle. Avoid reset
> by not initializing to default value everytime.
>
> Fixes: 67ae482a59e9 ("ALSA: hda: add member to store ratio for stripe control")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Sameer Pujar <spujar@nvidia.com>
How about to move the default sdo_limit setup into snd_hdac_bus_init()
instead? That's the place to be called only once.
thanks,
Takashi
> ---
> sound/hda/hdac_controller.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/sound/hda/hdac_controller.c b/sound/hda/hdac_controller.c
> index 011b17c..0e26e96 100644
> --- a/sound/hda/hdac_controller.c
> +++ b/sound/hda/hdac_controller.c
> @@ -538,7 +538,8 @@ bool snd_hdac_bus_init_chip(struct hdac_bus *bus, bool full_reset)
> * { ((num_channels * bits_per_sample * rate/48000) /
> * number of SDOs) >= 8 }
> */
> - bus->sdo_limit = 8;
> + if (!bus->sdo_limit)
> + bus->sdo_limit = 8;
>
> return true;
> }
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-08-19 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 14:44 [PATCH] ALSA: hda: avoid reset of sdo_limit Sameer Pujar
2020-08-19 14:53 ` Takashi Iwai [this message]
2020-08-19 15:21 ` Sameer Pujar
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=s5hmu2qhele.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=spujar@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=yang.jie@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox