From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Sound System <linux-sound@vger.kernel.org>,
sound-open-firmware@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Mete <yurnerolinux@yandex.com>
Subject: Re: Fwd: Garbled sound at start of a playback after some inactivity on said channel with DP/HDMI on RDNA devices
Date: Wed, 22 May 2024 06:09:49 +0700 [thread overview]
Message-ID: <32775b1a-7bc3-491f-bcab-af48d2d82d79@gmail.com> (raw)
In-Reply-To: <03d0fd01-278d-40ff-afcb-7107394b89eb@sirena.org.uk>
On 5/22/24 01:36, Mark Brown wrote:
> On Mon, May 13, 2024 at 03:08:02PM +0700, Bagas Sanjaya wrote:
>
>>> Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
>>> vendor: Sapphire PULSE driver: amdgpu v: kernel arch: RDNA-3 bus-ID: 03:00.0
>>> Device-2: AMD Raphael vendor: Gigabyte driver: amdgpu v: kernel
>>> arch: RDNA-2 bus-ID: 12:00.0 temp: 39.0 C
>
> You've CCed a bunch of Intel and NXP people for some reason but whatever
> this is it seems to be an AMD issue?
Yep, I found these addresses by `scripts/get_maintainer.pl
sound/soc/sof/amd/rembrandt.c` since I thought it was rembrandt
driver issue.
Thanks.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2024-05-21 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 8:08 Fwd: Garbled sound at start of a playback after some inactivity on said channel with DP/HDMI on RDNA devices Bagas Sanjaya
2024-05-21 18:36 ` Mark Brown
2024-05-21 23:09 ` Bagas Sanjaya [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=32775b1a-7bc3-491f-bcab-af48d2d82d79@gmail.com \
--to=bagasdotme@gmail.com \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.com \
--cc=yurnerolinux@yandex.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