Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Hills <mark@xwax.org>, alsa-devel@alsa-project.org
Subject: Re: rt5650 on HP Chromebook G5 Setzer faults
Date: Mon, 19 Dec 2022 18:13:36 -0600	[thread overview]
Message-ID: <06af4d22-1032-bc2e-b9da-ebfd966d144d@linux.intel.com> (raw)
In-Reply-To: <2212181230200.24243@stax.localdomain>

On 12/18/22 7:02 AM, Mark Hills wrote:
> HP Chromebook (11a, G5 "Setzer") uses snd_soc_sst_cht_bsw_rt5645 module
> and presents a device "rt5650".

can you share the result of 'aplay -l', wondering which platform driver 
you are using.
> Audio works briefly, until after about 30 seconds it's interrupted by a
> square wave or short buffer cycling.

If this is with the SOF driver, there's a known issue and a known 
workaround, please add this to /etc/modprobe.d/alsa-base.conf

options snd_sof sof_debug=1



  reply	other threads:[~2022-12-20  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-18 13:02 rt5650 on HP Chromebook G5 Setzer faults Mark Hills
2022-12-20  0:13 ` Pierre-Louis Bossart [this message]
2022-12-23 21:00   ` Mark Hills

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=06af4d22-1032-bc2e-b9da-ebfd966d144d@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=mark@xwax.org \
    /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