From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Shenghao Ding <shenghao-ding@ti.com>,
lgirdwood@gmail.com, perex@perex.cz,
pierre-louis.bossart@linux.intel.com, 13916275206@139.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
liam.r.girdwood@intel.com, bard.liao@intel.com,
mengdong.lin@intel.com, yung-chuan.liao@linux.intel.com,
baojun.xu@ti.com, kevin-lu@ti.com, navada@ti.com, tiwai@suse.de,
soyer@irl.hu
Subject: Re: [PATCH v7] ASoc: tas2783: Add tas2783 codec driver
Date: Wed, 7 Feb 2024 18:35:56 +0200 [thread overview]
Message-ID: <ZcOxbA_plPDqN3YA@smile.fi.intel.com> (raw)
In-Reply-To: <ZcOiCFlqsnyAEgl3@finisterre.sirena.org.uk>
On Wed, Feb 07, 2024 at 03:30:16PM +0000, Mark Brown wrote:
> On Wed, Feb 07, 2024 at 04:40:38PM +0200, Andy Shevchenko wrote:
> > On Wed, Feb 07, 2024 at 01:47:42PM +0800, Shenghao Ding wrote:
...
> > > + .max_register = 0x44ffffff,
>
> > I'm always wondering how this can work in debugfs when one tries to dump all
> > registers...
>
> regmap will filter out non-readable registers from what it shows in
> debugfs so sparse regmaps will end up much smaller than they might look.
> The debugfs code also has support for seeking into the output (since
> each register is a fixed size) so we'll only actually render whatever is
> being read in an individual read().
Thanks, good to know.
...
> > > +static const struct dev_pm_ops tas2783_sdca_pm = {
> > > + SET_SYSTEM_SLEEP_PM_OPS(tas2783_sdca_dev_suspend,
> > > + tas2783_sdca_dev_resume)
> > > + SET_RUNTIME_PM_OPS(tas2783_sdca_dev_suspend,
> > > + tas2783_sdca_dev_resume, NULL)
> > > +};
>
> > Use new PM macros.
>
> ...which are?
SYSTEM_SLEEP_PM_OPS()
RUNTIME_PM_OPS()
and pm_ptr() in the .driver.pm assignment.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-02-07 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 5:47 [PATCH v7] ASoc: tas2783: Add tas2783 codec driver Shenghao Ding
2024-02-07 14:40 ` Andy Shevchenko
2024-02-07 15:30 ` Mark Brown
2024-02-07 16:35 ` Andy Shevchenko [this message]
2024-02-07 16:45 ` Pierre-Louis Bossart
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=ZcOxbA_plPDqN3YA@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=13916275206@139.com \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=navada@ti.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.intel.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