From: "Philip Müller" <philm@manjaro.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jonathan LoBue <jlobue10@gmail.com>,
perex@perex.cz, tiwai@suse.com, shenghao-ding@ti.com,
kailang@realtek.com, alsa-devel@alsa-project.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
derekjohn.clark@gmail.com, luke@ljones.dev,
benato.denis96@gmail.com,
Kyle Gospodnetich <me@kylegospodneti.ch>,
Jan Drogehoff <sentrycraft123@gmail.com>,
Richard Alvarez <alvarez.richard@gmail.com>,
Miles Montierth <cyber_dopamine@intheblackmedia.com>,
"Chen, Robin" <robinchen@ti.com>,
Antheas Kapenekakis <lkml@antheas.dev>,
"Xu, Baojun" <baojun.xu@ti.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH] ALSA: hda/realtek: tas2781: Fix ROG ALLY X audio
Date: Fri, 11 Oct 2024 12:20:10 +0700 [thread overview]
Message-ID: <94782cf4-5317-49fb-bd8c-8dfc4eafae74@manjaro.org> (raw)
In-Reply-To: <CAGwozwEyhhDspUTyUwd9fqacKwoUwJJ=ZOHpJ5UfsaBs1kcx_w@mail.gmail.com>
On 15/8/24 19:58, Antheas Kapenekakis wrote:
> Hi everyone,
> I created the following Draft MR for the Ally firmware files:
> https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/272
>
> Please comment on it at your leisure. I will remove the Draft status once
> all the sign-off members verify it for correctness.
>
> @Shenghao: can you restate publicly the license of the firmware files and if
> there are no issues, sign-off on the MR?
>
> Best,
> Antheas
The firmware is now finally merged upstream:
https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/317/diffs
For now a symlink was added to make the current driver implementation by
Jonathan work:
https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/318/diffs
Jim and Robin from TI will adjust the tas2781_hda_i2c driver to load the
correct firmware per speaker vendor so the different optimized
protection parameters are given.
For example the following can be used to readout the GUID for
calibration data in UEFI BIOS:
status = efi.get_variable(efi_name, &efi_guid, &attr, &total_sz, data);
Example source:
find /sys/firmware/efi/efivars/ -name *-1f52* -print -exec hexdump -C {} \;
/sys/firmware/efi/efivars/CALI_DATA-1f52d2a1-bb3a-457d-bc09-43a3f4310a92
00000000 07 00 00 00 dd f5 15 41 4d ab bb 0f f4 11 bd 31
|.......AM......1|
00000010 bf 5e 97 00 00 00 00 24 2f 8d 10 3e 77 b9 7f 10
|.^.....$/..>w...|
00000020 f3 07 6e 2f b3 d0 93 00 00 00 00 24 00 00 00 00
|..n/.......$....|
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
00000050 00 00 00 00 f2 e1 73 66 8e 08 d9 2b 00 00 00 01
|......sf...+....|
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
00000080 00 00 00 00 |....|
00000084
--
Best, Philip
prev parent reply other threads:[~2024-10-11 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 4:53 Jonathan LoBue
2024-08-12 7:26 ` Takashi Iwai
2024-08-12 7:45 ` Antheas Kapenekakis
2024-08-12 11:27 ` Takashi Iwai
2024-08-15 12:58 ` Antheas Kapenekakis
2024-10-11 5:20 ` Philip Müller [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=94782cf4-5317-49fb-bd8c-8dfc4eafae74@manjaro.org \
--to=philm@manjaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=alvarez.richard@gmail.com \
--cc=baojun.xu@ti.com \
--cc=benato.denis96@gmail.com \
--cc=cyber_dopamine@intheblackmedia.com \
--cc=derekjohn.clark@gmail.com \
--cc=jlobue10@gmail.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=luke@ljones.dev \
--cc=mario.limonciello@amd.com \
--cc=me@kylegospodneti.ch \
--cc=perex@perex.cz \
--cc=robinchen@ti.com \
--cc=sentrycraft123@gmail.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®