From: "Xu, Baojun" <baojun.xu@ti.com>
To: Gergo Koteles <soyer@irl.hu>, "tiwai@suse.de" <tiwai@suse.de>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"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>,
"Lu, Kevin" <kevin-lu@ti.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>,
"yung-chuan.liao@linux.intel.com"
<yung-chuan.liao@linux.intel.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"Ding, Shenghao" <shenghao-ding@ti.com>
Subject: Re: [EXTERNAL] Re: [PATCH v1 7/8] ALSA: hda/tas2781: Add tas2781 SPI-based driver
Date: Fri, 5 Apr 2024 15:51:36 +0000 [thread overview]
Message-ID: <a64f246f48f447bc959f9d7591fbc477@ti.com> (raw)
In-Reply-To: <a84dd52c7ff74f9c8b84ba2ce2f0a9c2c3f20dae.camel@irl.hu>
Hi Gergo,
Answer in line:
> From: Gergo Koteles <soyer@irl.hu>
> Sent: 27 March 2024 18:02
> To: Xu, Baojun; tiwai@suse.de
> Cc: robh+dt@kernel.org; andriy.shevchenko@linux.intel.com; lgirdwood@gmail.com; perex@perex.cz; pierre-louis.bossart@linux.intel.com; Lu, Kevin; 13916275206@139.com; alsa-devel@alsa-project.org; linux-kernel@vger.kernel.org; liam.r.girdwood@intel.com; yung-chuan.liao@linux.intel.com; broonie@kernel.org
> Subject: [EXTERNAL] Re: [PATCH v1 7/8] ALSA: hda/tas2781: Add tas2781 SPI-based driver
>
> Hi Baojun, On Tue, 2024-03-26 at 09: 09 +0800, Baojun Xu wrote: > Firmware binary load lib code for tas2781 spi driver. > > Signed-off-by: Baojun Xu <baojun. xu@ ti. com> > --- > sound/pci/hda/tas2781_spi_fwlib. c | 2374 +++++++++++++++++++++++++++++
> ZjQcmQRYFpfptBannerStart
> This message was sent from outside of Texas Instruments.
> Do not click links or open attachments unless you recognize the source of this email and know the content is safe.
>
> ZjQcmQRYFpfptBannerEnd
>
> Hi Baojun,
>
> On Tue, 2024-03-26 at 09:09 +0800, Baojun Xu wrote:
> > Firmware binary load lib code for tas2781 spi driver.
> >
> > Signed-off-by: Baojun Xu <baojun.xu@ti.com>
> > ---
> > sound/pci/hda/tas2781_spi_fwlib.c | 2374 +++++++++++++++++++++++++++++
> > 1 file changed, 2374 insertions(+)
> > create mode 100644 sound/pci/hda/tas2781_spi_fwlib.c
> >
>
> Is this firmware loading logic the same as the already merged tas2781-
> fmwlib? If yes, why don't you use that?
It's almost same, but one firmware was loaded in I2C mode as one I2C device
was probed, and operate slavers by address. And with SPI mode, we probe two
SPI devices in current case, so will load two firmware binary, and some
operation need to be processed as special case, for example, under SPI,
read need one byte shifted if page number is large than 1.
>
> Thanks,
> Gergo
>
>
next prev parent reply other threads:[~2024-04-05 15:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 1:08 [PATCH v1 1/8] ALSA: hda/tas2781: Add tas2781 SPI-based driver Baojun Xu
2024-03-26 1:08 ` [PATCH v1 2/8] " Baojun Xu
2024-03-26 15:00 ` Andy Shevchenko
2024-03-26 15:22 ` Takashi Iwai
2024-03-26 1:09 ` [PATCH v1 3/8] " Baojun Xu
2024-03-26 1:09 ` [PATCH v1 4/8] " Baojun Xu
2024-03-26 15:01 ` Andy Shevchenko
2024-03-26 15:03 ` Andy Shevchenko
2024-03-26 1:09 ` [PATCH v1 5/8] " Baojun Xu
2024-03-26 1:09 ` [PATCH v1 6/8] " Baojun Xu
2024-03-26 15:05 ` Pierre-Louis Bossart
2024-04-06 7:43 ` [EXTERNAL] " Xu, Baojun
2024-03-26 1:09 ` [PATCH v1 7/8] " Baojun Xu
2024-03-26 15:13 ` Pierre-Louis Bossart
2024-03-26 15:16 ` Andy Shevchenko
2024-03-26 15:15 ` Andy Shevchenko
2024-03-27 10:02 ` Gergo Koteles
2024-04-05 15:51 ` Xu, Baojun [this message]
2024-03-26 1:09 ` [PATCH v1 8/8] " Baojun Xu
2024-03-26 14:58 ` [PATCH v1 1/8] " Andy Shevchenko
2024-04-05 16:17 ` [EXTERNAL] " Xu, Baojun
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=a64f246f48f447bc959f9d7591fbc477@ti.com \
--to=baojun.xu@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.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=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh+dt@kernel.org \
--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