From: Cezary Rojewski <cezary.rojewski@intel.com>
To: broonie@kernel.org
Cc: tiwai@suse.com, perex@perex.cz, amade@asmblr.net,
linux-sound@vger.kernel.org, andriy.shevchenko@linux.intel.com,
Cezary Rojewski <cezary.rojewski@intel.com>
Subject: [PATCH v3 0/6] ASoC: Intel: catpt: Round of fixes and PM changes
Date: Fri, 28 Nov 2025 10:34:06 +0100 [thread overview]
Message-ID: <20251128093412.3949374-1-cezary.rojewski@intel.com> (raw)
Set of changes addressing gaps in DRAM offset checks, error paths and
PM.
Three fixes lead the way, all straight-forward. Followed up by a small
refactor to replace manual arithmetic with resource_xxx() API. The last
two relate to the power management.
The standing out PM change is removal of the catpt-driver as a
system-suspend (S3) blocker. This is a suggestion from Andy as indeed,
audio is not a critical component that should prevent the system from
going into S3. Whatever happens, the driver can recover on a follow up
resume (S3 -> S0).
All points below suggested by Andy.
Changes in v3:
- reordered the patches so that all 3 fixes are at the start of the
patchset and added missing 'Fixes:' tag
- small spacing adjustments in patch 2/6
Changes in v2:
- removed the last patch from v1 "ASoC: Intel: catpt: Drop
catpt_runtime_resume()"
- added new patch "ASoC: Intel: catpt: Switch to resource_xxx() API"
which refactors existing code that manupulates .start, .end and size
of resources to publicly available interface
- patches 1/6 and 3/6 have had their message justified to improve
readability
Cezary Rojewski (6):
ASoC: Intel: catpt: Fix error path in hw_params()
ASoC: Intel: catpt: Fix probing order of driver components
ASoC: Intel: catpt: Fix offset checks
ASoC: Intel: catpt: Switch to resource_xxx() API
ASoC: Intel: catpt: Do not ignore errors on runtime resume
ASoC: Intel: catpt: Do not block the system from suspending
sound/soc/intel/catpt/device.c | 26 ++++++++++++++++++--------
sound/soc/intel/catpt/loader.c | 19 ++++++++++---------
sound/soc/intel/catpt/pcm.c | 16 +++++++++-------
sound/soc/intel/catpt/sysfs.c | 2 +-
4 files changed, 38 insertions(+), 25 deletions(-)
--
2.25.1
next reply other threads:[~2025-11-28 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 9:34 Cezary Rojewski [this message]
2025-11-28 9:34 ` [PATCH v3 1/6] ASoC: Intel: catpt: Fix error path in hw_params() Cezary Rojewski
2025-11-28 9:34 ` [PATCH v3 2/6] ASoC: Intel: catpt: Fix probing order of driver components Cezary Rojewski
2025-11-28 9:34 ` [PATCH v3 3/6] ASoC: Intel: catpt: Fix offset checks Cezary Rojewski
2025-11-28 9:34 ` [PATCH v3 4/6] ASoC: Intel: catpt: Switch to resource_xxx() API Cezary Rojewski
2025-11-28 9:34 ` [PATCH v3 5/6] ASoC: Intel: catpt: Do not ignore errors on runtime resume Cezary Rojewski
2025-11-28 9:34 ` [PATCH v3 6/6] ASoC: Intel: catpt: Do not block the system from suspending Cezary Rojewski
2025-11-28 10:45 ` [PATCH v3 0/6] ASoC: Intel: catpt: Round of fixes and PM changes Andy Shevchenko
2025-11-28 11:47 ` Mark Brown
2025-11-28 13:50 ` Cezary Rojewski
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=20251128093412.3949374-1-cezary.rojewski@intel.com \
--to=cezary.rojewski@intel.com \
--cc=amade@asmblr.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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