From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
broonie@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 1/2] ASoC: cs35l56: Use Disco FEID and FEV to qualify firmware filenames
Date: Wed, 11 Nov 2026 10:03:47 +0000 [thread overview]
Message-ID: <82344831-b6ce-48ad-b7eb-f17e9db05c61@opensource.cirrus.com> (raw)
In-Reply-To: <7c2574fe-1741-4119-be48-e7d314015787@linux.dev>
On 11/11/2026 7:44 am, Pierre-Louis Bossart wrote:
> On 11/10/26 17:48, Richard Fitzgerald wrote:
>> Include the FunctionExtensionID (FEID) and FunctionExtensionVersion (FEV)
>> values from Disco as qualifiers on firmware names. This mechanism is
>> required to support new products that use CS35L56/57/62/63.
>>
>> Some manufacturers are starting to re-use SSIDs, and the time between
>> re-use is decreasing. The SSID is therefore no longer providing the
>> unique hardware identifier intended by the PCI spec.
>
> D'oh! It's crazy that with all the technology available it's still
> difficult to define unique IDs...
>
>> To ensure that the audio hardware can be uniquely identified, the FEID
>> and FEV will be included in the Disco for new products and must be
>> used to qualify the firmware filename (unless FEID==0). For products that
>> require an SSID match, the combination of SSID, FEID, FEV will be unique.
>
> until the next time when a firmware person doesn't update the DisCo
> properties and reuses an ID from a previous device?
>
This is more about ensuring that the Linux driver still works when they
_do_ add a non-zero FEID in their Disco.
next prev parent reply other threads:[~2026-11-11 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 16:48 [PATCH 0/2] ASoC: cs35l56: Consider SDCA FunctionExtension ID/Version for firmware name Richard Fitzgerald
2026-11-10 16:48 ` [PATCH 1/2] ASoC: cs35l56: Use Disco FEID and FEV to qualify firmware filenames Richard Fitzgerald
2026-11-11 7:44 ` Pierre-Louis Bossart
2026-11-11 10:03 ` Richard Fitzgerald [this message]
2026-11-10 16:48 ` [PATCH 2/2] ASoC: cs35l56: Add KUnit tests for FEID and FEV firmware names Richard Fitzgerald
2026-11-11 7:45 ` [PATCH 0/2] ASoC: cs35l56: Consider SDCA FunctionExtension ID/Version for firmware name Pierre-Louis Bossart
2026-11-11 18:26 ` Mark Brown
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=82344831-b6ce-48ad-b7eb-f17e9db05c61@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.dev \
/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®