public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ding, Shenghao" <shenghao-ding@ti.com>
To: Amadeusz Slawinski <amadeuszx.slawinski@linux.intel.com>
Cc: "andriy.shevchenko@linux.intel.com"
	<andriy.shevchenko@linux.intel.com>,
	"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>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>,
	"bard.liao@intel.com" <bard.liao@intel.com>,
	"mengdong.lin@intel.com" <mengdong.lin@intel.com>,
	"yung-chuan.liao@linux.intel.com"
	<yung-chuan.liao@linux.intel.com>, "Lu, Kevin" <kevin-lu@ti.com>,
	"tiwai@suse.de" <tiwai@suse.de>, "soyer@irl.hu" <soyer@irl.hu>,
	"Baojun.Xu@fpt.com" <Baojun.Xu@fpt.com>,
	"Navada Kanyana, Mukund" <navada@ti.com>,
	"broonie@kernel.org" <broonie@kernel.org>
Subject: RE: [EXTERNAL] Re: [PATCH v11] ASoc: tas2783: Add tas2783 codec driver
Date: Sat, 16 Mar 2024 12:44:40 +0000	[thread overview]
Message-ID: <4e2006ff96a446978dd1996eeaa42099@ti.com> (raw)
In-Reply-To: <2efb5250-25f3-465e-81fc-cb885027b481@linux.intel.com>

Thanks for your comments. Kindly see the feedback

> -----Original Message-----
> From: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
> Sent: Wednesday, March 6, 2024 12:05 AM
> To: Ding, Shenghao <shenghao-ding@ti.com>; broonie@kernel.org
> Cc: andriy.shevchenko@linux.intel.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; Lu, Kevin
> <kevin-lu@ti.com>; tiwai@suse.de; soyer@irl.hu; Baojun.Xu@fpt.com;
> Navada Kanyana, Mukund <navada@ti.com>
> Subject: [EXTERNAL] Re: [PATCH v11] ASoc: tas2783: Add tas2783 codec
> driver
> 
> On 3/5/2024 2:26 PM, Shenghao Ding wrote:
> > The tas2783 is a smart audio amplifier with integrated MIPI SoundWire
> > interface (Version 1.2.1 compliant), I2C, and I2S/TDM interfaces
> > designed for portable applications. An on-chip DSP supports Texas
> > Instruments SmartAmp speaker protection algorithm. The integrated
> > speaker voltage and current sense provides for real-time monitoring of
> loudspeakers.
> >
> > The ASoC component provides the majority of the functionality of the
> > device, all the audio functions.
> >
> > Signed-off-by: Shenghao Ding <shenghao-ding@ti.com>
> >
> > ---
> 
> ...
...
> > +struct tasdevice_priv {
> > +	struct snd_soc_component *component;
> 
> Apart from being assigned this field seems to be unused.
This field can help to get the point to "struct tasdevice_priv" in tasdevice_sdw_pcm_hw_free, 
tasdevice_sdw_hw_params, tasdevice_mute

> 
> > +	struct sdw_slave *sdw_peripheral;
> > +	enum sdw_slave_status status;
> 
> This one seems to be only used in tasdevice_update_status()? Does it really
> need to be kept in struct?
> 
> > +	struct sdw_bus_params params;
> 
> Unused?
> 
> > +	struct regmap *regmap;
> > +	struct device *dev;
> > +	unsigned char dspfw_binaryname[TAS2783_DSPFW_FILENAME_LEN];
> 
> This one also seems weird, it is mainly needed when loading FW and could be
> local to tasdevice_comp_probe(), although there is one dev_warn which uses
> it outside of it, but pretty sure it could be dropped.
> 
> > +	unsigned char dev_name[32];
> 
> Another unused field.
> 
> > +	unsigned int chip_id;
> 
> Another one that only seems to be assigned.
> 
> > +	bool pstream;
> > +	bool hw_init;
> > +	bool first_hw_init;
> > +};
> > +
> > +#endif /*__TAS2783_H__ */


  reply	other threads:[~2024-03-16 12:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 13:26 [PATCH v11] ASoc: tas2783: Add tas2783 codec driver Shenghao Ding
2024-03-05 16:03 ` Pierre-Louis Bossart
2024-03-10  0:47   ` [EXTERNAL] " Ding, Shenghao
2024-03-11 15:25     ` Pierre-Louis Bossart
2024-03-05 16:04 ` Amadeusz Sławiński
2024-03-16 12:44   ` Ding, Shenghao [this message]
2024-03-18  9:12     ` [EXTERNAL] " Amadeusz Sławiński
  -- strict thread matches above, loose matches on Subject: below --
2024-03-19 13:58 Shenghao Ding
2024-03-19 15:35 ` Pierre-Louis Bossart
2024-03-26 12:36   ` [EXTERNAL] " Ding, Shenghao
2024-03-26 15:00     ` 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=4e2006ff96a446978dd1996eeaa42099@ti.com \
    --to=shenghao-ding@ti.com \
    --cc=13916275206@139.com \
    --cc=Baojun.Xu@fpt.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.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=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