From: "Holalu Yogendra, Niranjan" <niranjan.hy@ti.com>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: "linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"cezary.rojewski@intel.com" <cezary.rojewski@intel.com>,
"peter.ujfalusi@linux.intel.com" <peter.ujfalusi@linux.intel.com>,
"yung-chuan.liao@linux.intel.com"
<yung-chuan.liao@linux.intel.com>,
"ranjani.sridharan@linux.intel.com"
<ranjani.sridharan@linux.intel.com>,
"kai.vehmanen@linux.intel.com" <kai.vehmanen@linux.intel.com>,
"pierre-louis.bossart@linux.dev" <pierre-louis.bossart@linux.dev>,
"Xu, Baojun" <baojun.xu@ti.com>,
"Ding, Shenghao" <shenghao-ding@ti.com>,
"Kasargod, Sandeep" <sandeepk@ti.com>,
"Hampiholi, Vallabha" <v-hampiholi@ti.com>
Subject: RE: [EXTERNAL] Re: [PATCH v2 2/4] ASoC: tac5xx2-sdw: add soundwire based codec driver
Date: Mon, 30 Mar 2026 11:56:34 +0000 [thread overview]
Message-ID: <25d0ce626bd34dfc9e79d7fdc776f464@ti.com> (raw)
In-Reply-To: <acZgZnup3ENYl9SS@opensource.cirrus.com>
> On 16:18-20260327, Charles Keepax wrote:
> Subject: : [PATCH v2 2/4] ASoC: tac5xx2-sdw: add soundwire based codec driver
> On Thu, Mar 26, 2026 at 11:47:10PM +0530, Niranjan H Y wrote:
> > + SDW_SLAVE_ENTRY(0x0102, 0x2883, 0),
> > + {},
> > +};
>
..
> dodgy DisCo or hardware issues that make use difficult, so
> this is more of a long term goal. From scanning the driver here
> I am guessing perhaps the firmware download might not work so
> well with your current parts. But a lot of the rest looks like
> it would assuming the DisCo is all correct.
Thanks for the suggestion. I will start testing the class driver
Implementation for the current devices to identify any gaps and
start contributing. The plan is to go with class driver for next HW version.
Regards
Niranjan
next prev parent reply other threads:[~2026-03-30 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 18:17 [PATCH v2 1/4] ASoC: SDCA: make q78_get_volsw and q78_put_volsw extern Niranjan H Y
2026-03-26 18:17 ` [PATCH v2 2/4] ASoC: tac5xx2-sdw: add soundwire based codec driver Niranjan H Y
2026-03-27 10:48 ` Charles Keepax
2026-03-30 11:56 ` Holalu Yogendra, Niranjan [this message]
2026-03-26 18:17 ` [PATCH v2 3/4] ASoC: sdw_utils: TI amp utility for tac5xx2 family Niranjan H Y
2026-03-26 18:17 ` [PATCH v2 4/4] ASoC: tac5xx2-sdw: ACPI match for intel mtl platform Niranjan H Y
2026-03-27 10:49 ` [PATCH v2 1/4] ASoC: SDCA: make q78_get_volsw and q78_put_volsw extern Charles Keepax
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=25d0ce626bd34dfc9e79d7fdc776f464@ti.com \
--to=niranjan.hy@ti.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sandeepk@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.com \
--cc=v-hampiholi@ti.com \
--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