From: Jon Hunter <jonathanh@nvidia.com>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Takashi Iwai" <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Cezary Rojewski <cezary.rojewski@intel.com>,
Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Mohan Kumar D <mkumard@nvidia.com>
Subject: Re: [PATCH v2 2/4] ALSA: hda: Rework snd_hdac_stream_reset() to use macros
Date: Wed, 5 Oct 2022 21:16:34 +0100 [thread overview]
Message-ID: <1b154a54-381a-a8f6-f0ce-20bce05f27fc@nvidia.com> (raw)
In-Reply-To: <cd3918c8-64c2-fc8f-c184-3fec3ae01e3c@linux.intel.com>
On 05/10/2022 15:47, Amadeusz Sławiński wrote:
...
> Well in worse case we can revert the patch in question, but I would like
> to get it working...
>
> Maybe also try to raise timeout to 1000, as what original code called
> timeout, was actually number of retries? So 300 * udelay(3) which is
> more or less 900us, so we can round it up for test?
>
> I mean, something like:
>
> --- a/sound/hda/hdac_stream.c
> +++ b/sound/hda/hdac_stream.c
> @@ -176,7 +176,7 @@ void snd_hdac_stream_reset(struct hdac_stream *azx_dev)
> snd_hdac_stream_updateb(azx_dev, SD_CTL, 0, SD_CTL_STREAM_RESET);
>
> /* wait for hardware to report that the stream entered reset */
> - snd_hdac_stream_readb_poll(azx_dev, SD_CTL, val, (val &
> SD_CTL_STREAM_RESET), 3, 300);
> + snd_hdac_stream_readb_poll(azx_dev, SD_CTL, val, (val &
> SD_CTL_STREAM_RESET), 3, 1000);
>
> if (azx_dev->bus->dma_stop_delay && dma_run_state)
> udelay(azx_dev->bus->dma_stop_delay);
> @@ -184,7 +184,7 @@ void snd_hdac_stream_reset(struct hdac_stream *azx_dev)
> snd_hdac_stream_updateb(azx_dev, SD_CTL, SD_CTL_STREAM_RESET, 0);
>
> /* wait for hardware to report that the stream is out of reset */
> - snd_hdac_stream_readb_poll(azx_dev, SD_CTL, val, !(val &
> SD_CTL_STREAM_RESET), 3, 300);
> + snd_hdac_stream_readb_poll(azx_dev, SD_CTL, val, !(val &
> SD_CTL_STREAM_RESET), 3, 1000);
>
> /* reset first position - may not be synced with hw at this
> time */
> if (azx_dev->posbuf)
>
>
> in addition to Takashi suggestion?
Thanks. Tried that on top of Takaski's patch but still not working :-(
Jon
--
nvpublic
next prev parent reply other threads:[~2022-10-05 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 14:15 [PATCH v2 0/4] hda: Minor cleanups Amadeusz Sławiński
2022-08-18 14:15 ` [PATCH v2 1/4] ALSA: hda: Move stream-register polling macros Amadeusz Sławiński
2022-08-18 14:15 ` [PATCH v2 2/4] ALSA: hda: Rework snd_hdac_stream_reset() to use macros Amadeusz Sławiński
2022-10-05 12:10 ` Jon Hunter
2022-10-05 12:29 ` Takashi Iwai
2022-10-05 13:52 ` Jon Hunter
2022-10-05 14:07 ` Takashi Iwai
2022-10-05 14:26 ` Jon Hunter
2022-10-05 14:47 ` Amadeusz Sławiński
2022-10-05 20:16 ` Jon Hunter [this message]
2022-10-06 8:45 ` Jon Hunter
2022-10-07 8:49 ` Amadeusz Sławiński
2022-08-18 14:15 ` [PATCH v2 3/4] ALSA: hda: Remove unused MAX_PIN_CONFIGS constant Amadeusz Sławiński
2022-08-18 14:15 ` [PATCH v2 4/4] ALSA: hda: Remove unused defines Amadeusz Sławiński
2022-08-19 12:05 ` [PATCH v2 0/4] hda: Minor cleanups 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=1b154a54-381a-a8f6-f0ce-20bce05f27fc@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=cezary.rojewski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®