From: Takashi Iwai <tiwai@suse.de>
To: Jonathan LoBue <jlobue10@gmail.com>
Cc: 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>,
Antheas Kapenekakis <lkml@antheas.dev>,
Richard Alvarez <alvarez.richard@gmail.com>,
Miles Montierth <cyber_dopamine@intheblackmedia.com>
Subject: Re: [PATCH] ALSA: hda/realtek: tas2781: Fix ROG ALLY X audio
Date: Mon, 12 Aug 2024 09:26:46 +0200 [thread overview]
Message-ID: <87frra2ocp.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240812045325.47736-1-jlobue10@gmail.com>
On Mon, 12 Aug 2024 06:53:25 +0200,
Jonathan LoBue wrote:
>
> This patch enables the TI TAS2781 amplifier SoC for the ASUS ROG ALLY X.
> This is a design change from the original ASUS ROG ALLY, creating the need
> for this patch. All other Realtek Codec settings seem to be re-used from
> the original ROG ALLY design (on the ROG ALLY X). This patch maintains the
> previous settings for the Realtek codec portion, but enables the I2C
> binding for the TI TAS2781 amplifier (instead of the Cirrus CS35L41 amp
> used on the original ASUS ROG ALLY).
>
> One other requirement must be met for audio to work on the ASUS ROG ALLY X.
> A proper firmware file in the correct location with a proper symlink. We
> had reached out to TI engineers and confirmed that the firmware found in
> the Windows' driver package has a GPL license. Bazzite Github is hosting
> this firmware file for now until proper linux-firmware upstreaming can
> occur. https://github.com/ublue-os/bazzite
>
> This firmware file should be placed in
> /usr/lib/firmware/ti/tas2781/TAS2XXX1EB3.bin with a symlink to it from
> /usr/lib/firmware/TAS2XXX1EB3.bin
>
> Co-developed by: Kyle Gospodnetich <me@kylegospodneti.ch>
> Signed-off-by: Kyle Gospodnetich <me@kylegospodneti.ch>
> Co-developed by: Jan Drogehoff <sentrycraft123@gmail.com>
> Signed-off-by: Jan Drogehoff <sentrycraft123@gmail.com>
> Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
> Tested-by: Richard Alvarez <alvarez.richard@gmail.com>
> Tested-by: Miles Montierth <cyber_dopamine@intheblackmedia.com>
> Signed-off-by: Jonathan LoBue <jlobue10@gmail.com>
Applied to for-next branch.
Meanwhile, could you ask TI guys to include the missing firmware files
in linux-firmware git tree, too?
thanks,
Takashi
next prev parent reply other threads:[~2024-08-12 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 4:53 [PATCH] ALSA: hda/realtek: tas2781: Fix ROG ALLY X audio Jonathan LoBue
2024-08-12 7:26 ` Takashi Iwai [this message]
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
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=87frra2ocp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=alvarez.richard@gmail.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=me@kylegospodneti.ch \
--cc=perex@perex.cz \
--cc=sentrycraft123@gmail.com \
--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