[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZcOiCFlqsnyAEgl3@finisterre.sirena.org.uk>
Date: Wed, 7 Feb 2024 15:30:16 +0000
From: Mark Brown <broonie@...nel.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Shenghao Ding <shenghao-ding@...com>, lgirdwood@...il.com,
perex@...ex.cz, pierre-louis.bossart@...ux.intel.com,
13916275206@....com, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org, liam.r.girdwood@...el.com,
bard.liao@...el.com, mengdong.lin@...el.com,
yung-chuan.liao@...ux.intel.com, baojun.xu@...com, kevin-lu@...com,
navada@...com, tiwai@...e.de, soyer@....hu
Subject: Re: [PATCH v7] ASoc: tas2783: Add tas2783 codec driver
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:
> > +static const struct regmap_config tasdevice_regmap = {
> > + .reg_bits = 32,
> > + .val_bits = 8,
> > + .readable_reg = tas2783_readable_register,
> > + .volatile_reg = tas2783_volatile_register,
> > + .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().
> > +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?
Download attachment "signature.asc" of type "application/pgp-signature" (485 bytes)
Powered by blists - more mailing lists