Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: broonie@kernel.org
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
	oder_chiou@realtek.com, "Shuming [范書銘]" <shumingf@realtek.com>,
	"Pierre-Louis Bossart" <pierre-louis.bossart@linux.intel.com>,
	vinod.koul@linaro.org, "vkoul@kernel.org" <vkoul@kernel.org>,
	"Katragadda, Mastan" <mastan.katragadda@amd.com>,
	"kondaveeti, Arungopal" <arungopal.kondaveeti@amd.com>,
	"Hiregoudar, Basavaraj" <Basavaraj.Hiregoudar@amd.com>,
	"Dommati, Sunil-kumar" <Sunil-kumar.Dommati@amd.com>,
	"Mario Limonciello" <mario.limonciello@amd.com>,
	"Bard Liao" <yung-chuan.liao@linux.intel.com>
Subject: Re: [BUG] ASoC: Use the maple tree register cache for RealTek SoundWire CODECs
Date: Mon, 26 Jun 2023 19:00:31 +0530	[thread overview]
Message-ID: <b8af4050-85e7-6974-9c44-c26cb6962972@amd.com> (raw)
In-Reply-To: <20230609-asoc-rt-sdw-maple-v1-0-85ee50c93905@kernel.org>

Hello,

With cache type changing to maple tree for SoundWire Codec patch series, we are observing
rcu warnings with AMD SoundWire stack.

Below are the pastebin links for rcu warnings dmesg logs.

https://pastebin.com/6sadwNCw <https://pastebin.com/6sadwNCw>

https://pastebin.com/zwhfUKGf <https://pastebin.com/zwhfUKGf>

Acquiring rcu lock in between register read/writes causes context switch.

In AMD SoundWire manager xfer_msg() callback, we are using read_poll_timeout logic.
Below is the link.
https://elixir.bootlin.com/linux/v6.4-rc7/source/drivers/soundwire/amd_manager.c#L177

As per our understanding, we need to go with busy wait rather than using usleep_range()
which will be invoked by read_poll_timeout() logic.

Could you please suggest us how to fix this issue?

Thanks,
Vijendar


  parent reply	other threads:[~2023-06-26 13:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 14:27 [PATCH 0/8] ASoC: Use the maple tree register cache for RealTek SoundWire CODECs Mark Brown
2023-06-10 14:27 ` [PATCH 1/8] ASoC: rt700: Use maple tree register cache Mark Brown
2023-06-10 14:27 ` [PATCH 2/8] ASoC: rt711: " Mark Brown
2023-06-10 14:27 ` [PATCH 3/8] ASoC: rt712: " Mark Brown
2023-06-10 14:27 ` [PATCH 4/8] ASoC: rt715: " Mark Brown
2023-06-10 14:27 ` [PATCH 5/8] ASoC: rt722: " Mark Brown
2023-06-10 14:27 ` [PATCH 6/8] ASoC: rt1308: " Mark Brown
2023-06-10 14:27 ` [PATCH 7/8] ASoC: rt1316: " Mark Brown
2023-06-10 14:27 ` [PATCH 8/8] ASoC: rt1318: " Mark Brown
2023-06-14  1:15 ` [PATCH 0/8] ASoC: Use the maple tree register cache for RealTek SoundWire CODECs Liao, Bard
2023-06-15 12:53 ` Mark Brown
2023-06-26 13:30 ` Mukunda,Vijendar [this message]
2023-06-26 13:29   ` [BUG] " Mark Brown
2023-06-26 14:39     ` Mukunda,Vijendar
2023-06-27  5:20       ` Mukunda,Vijendar

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=b8af4050-85e7-6974-9c44-c26cb6962972@amd.com \
    --to=vijendar.mukunda@amd.com \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arungopal.kondaveeti@amd.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=mario.limonciello@amd.com \
    --cc=mastan.katragadda@amd.com \
    --cc=oder_chiou@realtek.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=shumingf@realtek.com \
    --cc=vinod.koul@linaro.org \
    --cc=vkoul@kernel.org \
    --cc=yung-chuan.liao@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