From: Takashi Iwai <tiwai@suse.de>
To: Aaron Ma <aaron.ma@canonical.com>
Cc: shenghao-ding@ti.com, kevin-lu@ti.com, baojun.xu@ti.com,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
perex@perex.cz, tiwai@suse.com
Subject: Re: [PATCH] ALSA: hda/ASOC tas2781: align the path of firmware
Date: Thu, 25 Apr 2024 10:45:36 +0200 [thread overview]
Message-ID: <87a5lhbzkf.wl-tiwai@suse.de> (raw)
In-Reply-To: <11d5d3db-d5ba-4a02-9c58-400075f2918e@canonical.com>
On Thu, 25 Apr 2024 10:40:50 +0200,
Aaron Ma wrote:
>
>
> On 4/25/24 16:36, Takashi Iwai wrote:
> > On Thu, 25 Apr 2024 09:54:17 +0200,
> > Aaron Ma wrote:
> >>
> >>
> >> On 4/25/24 15:52, Takashi Iwai wrote:
> >>
> >> On Thu, 25 Apr 2024 09:20:00 +0200,
> >> Aaron Ma wrote:
> >> TI upstream the files in ti/tas2781 for
> >> linux-firmware.
> >> Make the driver find the correct files.
> >> Note that the upstream linux-firmware provides
> >> symlinks to
> >> ti/tas2781/* files, so it's not "incorrect", so far :)
> >>
> >> $ find . -iname TIAS2781RCA2.bin
> >> ./ti/tas2781/TIAS2781RCA2.bin
> >>
> >> Only one bin file found.
> >> Could you point it out clearly?
> >
> > See WHENCE file. It has "Link:" entries, and copy-firmware.sh creates
> > corresponding symlinks.
>
> Oh, missed it.
> Retrieve the patch.
OK. I guess ti/*/* is a better place for newer firmware files
(and likely intended by TI), but it's up to TI whether we should
update or not for newer chips. Let's see.
thanks,
Takashi
prev parent reply other threads:[~2024-04-25 8:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 7:20 [PATCH] ALSA: hda/ASOC tas2781: align the path of firmware Aaron Ma
2024-04-25 7:52 ` Takashi Iwai
2024-04-25 7:54 ` Aaron Ma
2024-04-25 8:36 ` Takashi Iwai
2024-04-25 8:40 ` Aaron Ma
2024-04-25 8:45 ` Takashi Iwai [this message]
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=87a5lhbzkf.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=aaron.ma@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=kevin-lu@ti.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).