mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: linux-kernel.supreme403@8alias.com
To: Antheas Kapenekakis <lkml@antheas.dev>
Cc: tiwai@suse.com,"Ding,
	Shenghao"
	<shenghao-ding@ti.com>,perex@perex.cz,baojun.xu@ti.com,kevin-lu@ti.com,sen@ti.com,matthew.schwartz@linux.dev,linux-sound@vger.kernel.org,linux-kernel@vger.kernel.org
Subject: Re: [RESEND] ALSA: hda/tas2781: TP3407SA evidence for the January custom calibration address patch
Date: Sun, 1 Nov 2026 23:23:51 +0100 (CET)	[thread overview]
Message-ID: <179357183245.7.3137161079355845805.1738723974@8alias.com> (raw)
In-Reply-To: <CAGwozwGQvRbwg82M4Myv4GQJhCPEhjyN__6DJ8UdMb8o0V_Zcg@mail.gmail.com>


Hi Antheas,


Any news on resending this patch? Is there anything you need from me before it can move forward?



Thanks,
assembledev



> On Mon, 5 Oct 2026 at 20:04, <linux-kernel.supreme403@8alias.com> wrote:
>
>>
>> Hi Antheas and sound/TI maintainers,
>>
>> Resending as plain text because LKML rejected the previous message for containing an HTML part.
>> ...
>> Limits: only the primary amplifier was read on hardware, and the final register snapshot was taken idle. The listening result is subjective; there is no calibrated SPL measurement or controlled same-volume A/B. Current mainline and for-next were not built and booted as full kernels.
>>
>> Unlike the January Ally X test, this machine's OEM and firmware layouts differ. This report does not claim to fix the Ally X's separate symptom. Commit 4fe238513407 introduced the custom-node parser with the BASIC-only assignment and appears to be the appropriate Fixes target.
>>
>> DSP SHA256:
>>  a29f522c22cdb203eb1af84846838b5ef76c3a2c721760c7a898dd35f9ce1430
>> Public firmware:
>> https://gitlab.com/kernel-firmware/linux-firmware/-/raw/20260410/ti/audio/tas2781/TAS2XXX10A40.bin
>> Original patch:
>> https://lore.kernel.org/all/20260107093134.583873-1-lkml@antheas.dev/
>>
>> OpenAI Codex (LLM) assisted with diagnosing the quiet speakers, validating the existing patch, preparing a local reproducer and drafting this hardware report. The kernel change is your January proposal.
>>
>
> The Ally X had a different issue so we never merged that fix. The
> commit body would need to be amended but we should be able to merge
> this.
>
> Does anyone else have any suggestions? If not I can plan to resend the
> fix in a few days. I will not be able to do the testing for it (no
> affected devices)
>
> Antheas
>
>> Assisted-by: LLM
>>
>> Thanks,
>> assembledev
>>
>
>



  reply	other threads:[~2026-11-01 22:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <179122226568.6.10663878730330541363.1670962442@8alias.com>
     [not found] ` <P3C8cUq--F-9@tutamail.com>
2026-10-05 18:04   ` linux-kernel.supreme403
2026-10-07 11:03     ` Antheas Kapenekakis
2026-11-01 22:23       ` linux-kernel.supreme403 [this message]
2026-11-02 10:23         ` Antheas Kapenekakis

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=179357183245.7.3137161079355845805.1738723974@8alias.com \
    --to=linux-kernel.supreme403@8alias.com \
    --cc=baojun.xu@ti.com \
    --cc=kevin-lu@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=lkml@antheas.dev \
    --cc=matthew.schwartz@linux.dev \
    --cc=perex@perex.cz \
    --cc=sen@ti.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

all inboxes | Powered by JetHome®