From: Jude Gyimah <jude.gyimah87@gmail.com>
To: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz, tiwai@suse.com
Cc: chancel.liu@nxp.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jude Gyimah <jude.gyimah87@gmail.com>
Subject: [PATCH 0/3] ASoC: fsl: fix missing GENERIC_BITREVERSE and REGMAP_MMIO dependencies
Date: Wed, 4 Nov 2026 14:49:57 +0100 [thread overview]
Message-ID: <20261104135000.3723017-1-jude.gyimah87@gmail.com> (raw)
Each of these drivers can be built into vmlinux while the code
providing a symbol it calls is a module, which fails to link. The
same shape in 3 drivers, so they are here as one series.
Affected: fsl_aud2htx, fsl_xcvr, lpc3xxx-i2s.
The fix is a select rather than a depends on: the providers have no
prompt of their own and are only ever enabled by a select, so a
depends on would leave these drivers unselectable.
Each was reproduced on v7.3, x86_64, by a vmlinux link that failed on
the named symbol, and each links once the select is added.
Found with kreach, a static check that compares what Kconfig allows
against the symbols the compiled objects actually reference.
The checker is at https://github.com/JGyimah/kreach, and the
reproducer configuration for each finding is published with it
under results/.
Jude Gyimah (3):
ASoC: fsl_aud2htx: select missing dependencies
ASoC: fsl: lpc3xxx-i2s: select REGMAP_MMIO
ASoC: fsl_xcvr: select BITREVERSE
sound/soc/fsl/Kconfig | 4 ++++
1 file changed, 4 insertions(+)
--
2.43.0
next reply other threads:[~2026-11-04 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 13:49 Jude Gyimah [this message]
2026-11-04 13:49 ` [PATCH 1/3] ASoC: fsl_aud2htx: select missing dependencies Jude Gyimah
2026-11-04 13:49 ` [PATCH 2/3] ASoC: fsl: lpc3xxx-i2s: select REGMAP_MMIO Jude Gyimah
2026-11-04 13:50 ` [PATCH 3/3] ASoC: fsl_xcvr: select BITREVERSE Jude Gyimah
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=20261104135000.3723017-1-jude.gyimah87@gmail.com \
--to=jude.gyimah87@gmail.com \
--cc=broonie@kernel.org \
--cc=chancel.liu@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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®