From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Gergo Koteles <soyer@irl.hu>,
Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 2/2] ALSA: hda/tas2563: Add tas2563 HDA driver
Date: Tue, 5 Dec 2023 10:12:23 -0600 [thread overview]
Message-ID: <fc19ccbe-2e06-42f5-b968-446f8c08ec22@linux.intel.com> (raw)
In-Reply-To: <a530e70a-2491-4270-b582-cd493d1512b1@linux.intel.com>
>>>> +static const struct dev_pm_ops tas2563_hda_pm_ops = {
>>>> + SYSTEM_SLEEP_PM_OPS(tas2563_system_suspend, tas2563_system_resume)
>>>
>>> where's the pm_runtime stuff?
>>>
>>
>> The amp stores its state in software shutdown mode.
>> The tas2563_hda_playback_hook wakes/shutdowns the amp, not the
>> pm_runtime.
>
> My point was that you have all these pm_runtime_ calls in the code, but
> nothing that provides pm_runtime suspend-resume functions so not sure
> what exactly the result is?
if the inspiration was the tas2781, then see below it does have a
RUNTIME_PM_OPS line as well as runtime_suspend/resume routines.
static const struct dev_pm_ops tas2781_hda_pm_ops = {
RUNTIME_PM_OPS(tas2781_runtime_suspend, tas2781_runtime_resume, NULL)
SYSTEM_SLEEP_PM_OPS(tas2781_system_suspend, tas2781_system_resume)
};
next prev parent reply other threads:[~2023-12-05 16:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 23:45 [PATCH 0/2] ALSA: hda/tas2563: Add tas253 HDA driver Gergo Koteles
2023-12-04 23:45 ` [PATCH 1/2] ASoc: tas2563: DSP Firmware loading support Gergo Koteles
2023-12-05 0:05 ` Pierre-Louis Bossart
2023-12-05 1:11 ` Gergo Koteles
2023-12-04 23:45 ` [PATCH 2/2] ALSA: hda/tas2563: Add tas2563 HDA driver Gergo Koteles
2023-12-05 0:22 ` Pierre-Louis Bossart
2023-12-05 1:31 ` Gergo Koteles
2023-12-05 16:01 ` Pierre-Louis Bossart
2023-12-05 16:12 ` Pierre-Louis Bossart [this message]
2023-12-05 16:13 ` Mark Brown
2023-12-05 16:59 ` Gergo Koteles
2023-12-05 17:22 ` Pierre-Louis Bossart
2023-12-06 16:07 ` Amadeusz Sławiński
2023-12-07 13:00 ` Andy Shevchenko
2023-12-10 2:02 ` kernel test robot
2023-12-07 1:05 ` [PATCH 0/2] ALSA: hda/tas2563: Add tas253 " Gergo Koteles
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=fc19ccbe-2e06-42f5-b968-446f8c08ec22@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
--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 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.