All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Everaars <robineveraars@pm.me>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>,
	linux-sound@vger.kernel.org
Cc: venkataprasad.potturu@amd.com, lgirdwood@gmail.com,
	broonie@kernel.org, linux-kernel@vger.kernel.org,
	Mario Limonciello <Mario.Limonciello@amd.com>,
	"Dommati, Sunil-kumar" <Sunil-kumar.Dommati@amd.com>,
	Syed Saba Kareem <syed.sabakareem@amd.com>
Subject: Re: ASoC: amd: acp-pdm: full-scale burst on every DMIC capture start
Date: Thu, 13 Aug 2026 12:26:35 +0000	[thread overview]
Message-ID: <20260813122632.9851-1-robineveraars@pm.me> (raw)
In-Reply-To: <20260813121645.15370-1-robineveraars@pm.me>


[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]

One clarification about the isolated -EIO mentioned above: I removed patch 2,
rebuilt and rebooted into the earlier patch-1-only module. Its SHA-256 was:

  cd55e119961b80066c66ae7abb5f05ca97fa2747de7887a17ee45c724f19fc9d

The first runtime-suspended capture after that reboot again returned -EIO
before delivering data, with no matching kernel diagnostic. The next three
runtime-suspended captures each delivered all 48000 frames with no clipped or
>=99% full-scale samples.

I therefore do not attribute the isolated -EIO to patch 2. The reproducible
patch-2 regression remains the scheduling-while-atomic failure from msleep()
in acp63_pdm_dai_trigger() during active-capture resume.

Thanks,
Robin

[-- Attachment #1.2: publickey - robineveraars@pm.me - 0x8B6BA132.asc --]
[-- Type: application/pgp-keys, Size: 889 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 322 bytes --]

  reply	other threads:[~2026-08-13 12:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 18:11 ASoC: amd: acp-pdm: full-scale burst on every DMIC capture start Robin Everaars
2026-08-10  5:11 ` Mukunda,Vijendar
2026-08-11 12:33   ` Robin Everaars
2026-08-11 15:27     ` Mukunda,Vijendar
2026-08-12  9:38     ` Mukunda,Vijendar
2026-08-12 13:41       ` Robin Everaars
2026-08-13  5:10         ` Mukunda,Vijendar
2026-08-13 12:16           ` Robin Everaars
2026-08-13 12:26             ` Robin Everaars [this message]
2026-08-14  8:35               ` Mukunda,Vijendar
2026-08-24 13:47                 ` Robin Everaars
2026-08-27  6:44                   ` 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=20260813122632.9851-1-robineveraars@pm.me \
    --to=robineveraars@pm.me \
    --cc=Mario.Limonciello@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=syed.sabakareem@amd.com \
    --cc=venkataprasad.potturu@amd.com \
    --cc=vijendar.mukunda@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.