From: Takashi Iwai <tiwai@suse.de>
To: soxiebing <soxiebing@163.com>
Cc: tiwai@suse.de, linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: fix snd_hda_bus_reset when single_cmd is not supported
Date: Mon, 26 Aug 2024 12:01:42 +0200 [thread overview]
Message-ID: <87h6b7iovt.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240826091958.44375-1-soxiebing@163.com>
On Mon, 26 Aug 2024 11:19:58 +0200,
soxiebing wrote:
>
> >On Wed, 21 Aug 2024 03:42:38 +0200,
> >soxiebing wrote:
> >>
> >> From: songxiebing <songxiebing@kylinos.cn>
> >>
> >> When an azx_get_desponse timeout occurs, ensure that bus_reset
> >> can be used when fallback_to_single_cmd is not supported.
> >>
> >> Signed-off-by: songxiebing <songxiebing@kylinos.cn>
> >
> >Why do you need to change? Does it fix any real problem you faced?
>
> Thanks for reply, i am testing all these days, but the problem is
> still exists even if using bus reset.
>
> The problem i encountered is that hda_call_codec_resume returned
> timeout of 120 seconds(defined CONFIG_DPM_WATCHDOG)) when doing s4,
> azx_get_response timeout occured, it is a low probability event.
>
> To avoid exceeding 120s, can i change the count value to 3 in
> hda_set_power_state ?
So the change you suggested isn't for any real "fix" but to allow the
possible workaround with single_cmd to be applicable somehow in a
different form. Then we should rather try debugging the original
issue, instead of change it.
Does the response timeout happen *during* the S4 suspend, or during S4
resume, or after S4 resume?
To be noted, the behavior you changed is only for the single_cmd
option is set explicitly, so it's more or less the designed behavior,
and I don't think it's good to change blindly.
Takashi
next prev parent reply other threads:[~2024-08-26 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 1:42 [PATCH v1] ALSA: hda: fix snd_hda_bus_reset when single_cmd is not supported soxiebing
2024-08-21 7:11 ` Takashi Iwai
2024-08-26 9:19 ` [PATCH] " soxiebing
2024-08-26 10:01 ` Takashi Iwai [this message]
2024-08-27 3:30 ` soxiebing
2024-08-27 5:53 ` 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=87h6b7iovt.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=soxiebing@163.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