From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Ding, Shenghao" <shenghao-ding@ti.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"perex@perex.cz" <perex@perex.cz>,
"pierre-louis.bossart@linux.intel.com"
<pierre-louis.bossart@linux.intel.com>,
"13916275206@139.com" <13916275206@139.com>,
"zhourui@huaqin.com" <zhourui@huaqin.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Salazar, Ivan" <i-salazar@ti.com>,
"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>,
"Yue, Jaden" <jaden-yue@ti.com>,
"yung-chuan.liao@linux.intel.com"
<yung-chuan.liao@linux.intel.com>, "Rao, Dipa" <dipa@ti.com>,
"yuhsuan@google.com" <yuhsuan@google.com>,
"Lo, Henry" <henry.lo@ti.com>, "tiwai@suse.de" <tiwai@suse.de>,
"Xu, Baojun" <baojun.xu@ti.com>,
"Baojun.Xu@fpt.com" <Baojun.Xu@fpt.com>,
"judyhsiao@google.com" <judyhsiao@google.com>,
"Navada Kanyana, Mukund" <navada@ti.com>,
"cujomalainey@google.com" <cujomalainey@google.com>,
"Kutty, Aanya" <aanya@ti.com>,
"Mahmud, Nayeem" <nayeem.mahmud@ti.com>,
"savyasanchi.shukla@netradyne.com"
<savyasanchi.shukla@netradyne.com>,
"flaviopr@microsoft.com" <flaviopr@microsoft.com>,
"Ji, Jesse" <jesse-ji@ti.com>,
"darren.ye@mediatek.com" <darren.ye@mediatek.com>,
"antheas.dk@gmail.com" <antheas.dk@gmail.com>,
"Jerry2.Huang@lcfuturecenter.com"
<Jerry2.Huang@lcfuturecenter.com>,
"jim.shil@goertek.com" <jim.shil@goertek.com>
Subject: Re: [EXTERNAL] Re: [PATCH v1] ASoC: tas2781: mark const variables tas2563_dvc_table as __maybe_unused
Date: Mon, 26 Aug 2024 13:02:31 +0300 [thread overview]
Message-ID: <ZsxStyum6bU4z3eS@smile.fi.intel.com> (raw)
In-Reply-To: <b9293d922c194d62b845c4ec6b1bf2b6@ti.com>
On Sat, Aug 24, 2024 at 06:33:41AM +0000, Ding, Shenghao wrote:
> > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Sent: Friday, August 23, 2024 9:34 PM
> > On Fri, Aug 23, 2024 at 02:24:17AM +0000, Ding, Shenghao wrote:
> > > > From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > > Sent: Thursday, August 22, 2024 9:37 PM
> > > > To: Ding, Shenghao <shenghao-ding@ti.com> On Thu, Aug 22, 2024 at
> > > > 02:32:02PM +0800, Shenghao Ding wrote:
...
> > > > > /* pow(10, db/20) * pow(2,30) */
> > > > > -static const unsigned char tas2563_dvc_table[][4] = {
> > > > > +static const __maybe_unused unsigned char tas2563_dvc_table[][4]
> > > > > += {
> > > > > { 0X00, 0X00, 0X00, 0X00 }, /* -121.5db */
> > > > > { 0X00, 0X00, 0X03, 0XBC }, /* -121.0db */
> > > > > { 0X00, 0X00, 0X03, 0XF5 }, /* -120.5db */
> > > >
> > > > As far as I can see in the latest Linux Next the above mentioned
> > > > table is used solely in sound/soc/codecs/tas2781-i2c.c. Why not
> > > > moving it to the C file instead?
> > > We have a big plan to implement the digital gain for tas2563 in the
> > > side codec driver too, so abstracted this table into a separated header file.
> >
> > So, this __maybe_unused is a temporary stub, correct? Just don't forget to
> > remove it when the mentioned functionality will be ready.
> >
> > Thanks for the explanation.
> To add __maybe_unused is not temporary, because this driver support both
> tas2563 and tas2781, if the hardware only contains tas2781 chips,
> tas2563_dvc_table is obviously useless, so marked it as __maybe_unused.
You got me confused.
__maybe_unused is a compile-time (okay, link-time) attribute. If what you are
telling is true, why do you need it and can't use respective #ifdef?
Otherwise, why is it in the _header_ file and not in the C-file?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-08-26 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 6:32 [PATCH v1] ASoC: tas2781: mark const variables tas2563_dvc_table as __maybe_unused Shenghao Ding
2024-08-22 13:36 ` Andy Shevchenko
2024-08-23 2:24 ` [EXTERNAL] " Ding, Shenghao
2024-08-23 13:34 ` Andy Shevchenko
2024-08-24 6:33 ` Ding, Shenghao
2024-08-26 10:02 ` Andy Shevchenko [this message]
2024-08-22 16:17 ` Mark Brown
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=ZsxStyum6bU4z3eS@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=13916275206@139.com \
--cc=Baojun.Xu@fpt.com \
--cc=Jerry2.Huang@lcfuturecenter.com \
--cc=aanya@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=antheas.dk@gmail.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=darren.ye@mediatek.com \
--cc=dipa@ti.com \
--cc=flaviopr@microsoft.com \
--cc=henry.lo@ti.com \
--cc=i-salazar@ti.com \
--cc=jaden-yue@ti.com \
--cc=jesse-ji@ti.com \
--cc=jim.shil@goertek.com \
--cc=judyhsiao@google.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=navada@ti.com \
--cc=nayeem.mahmud@ti.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=savyasanchi.shukla@netradyne.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
--cc=yuhsuan@google.com \
--cc=yung-chuan.liao@linux.intel.com \
--cc=zhourui@huaqin.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