From: sashiko-bot@kernel.org
To: "David Heidelberg" <david@ixit.cz>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH RFC 2/3] ASoC: codecs: tfa98xx: add driver for TFA2 amplifiers
Date: Sun, 02 Aug 2026 12:48:55 +0000 [thread overview]
Message-ID: <20260802124855.ABB921F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260802-tfa98xx-upstream-v1-2-4dd55cdd658a@ixit.cz>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The i2c_device_id array fails to use named initializers.
--
--- Patch [2]: [PATCH RFC 2/3] ASoC: codecs: tfa98xx: add driver for TFA2 amplifiers ---
commit 4120c0a8b537c48d7609971c712e99479ca0e3ec
Author: David Heidelberg <david@ixit.cz>
ASoC: codecs: tfa98xx: add driver for TFA2 amplifiers
This commit adds a driver for the NXP/Goodix TFA98xx (TFA2) smart speaker
amplifiers, initially supporting the TFA9894 found on the OnePlus 6T.
The driver bypasses the built-in CoolFlux DSP and takes the amplifier input
straight from the TDM interface.
> diff --git a/sound/soc/codecs/tfa98xx.c b/sound/soc/codecs/tfa98xx.c
> new file mode 100644
> index 0000000000000..c84abb8db207a
> --- /dev/null
> +++ b/sound/soc/codecs/tfa98xx.c
[ ... ]
> +static const struct i2c_device_id tfa98xx_i2c_id[] = {
> + { "tfa9894", (kernel_ulong_t)&tfa9894_chip },
> + { }
> +};
[Severity: Low]
This isn't a bug, but should the tfa98xx_i2c_id array use named initializers
(such as .name = "tfa9894", .driver_data = ...) to align with the I2C
subsystem guidelines for initialized arrays of type struct i2c_device_id?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260802-tfa98xx-upstream-v1-0-4dd55cdd658a@ixit.cz?part=2
next prev parent reply other threads:[~2026-08-02 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 12:42 [PATCH RFC 0/3] Initial TFA2 family driver for tfa98xx David Heidelberg via B4 Relay
2026-08-02 12:42 ` David Heidelberg
2026-08-02 12:42 ` [PATCH RFC 1/3] dt-bindings: sound: Add NXP TFA98XX TFA2 amplifier binding David Heidelberg via B4 Relay
2026-08-02 12:42 ` David Heidelberg
2026-08-02 12:45 ` sashiko-bot
2026-08-03 21:39 ` Mark Brown
2026-08-02 12:42 ` [PATCH RFC 2/3] ASoC: codecs: tfa98xx: add driver for TFA2 amplifiers David Heidelberg via B4 Relay
2026-08-02 12:42 ` David Heidelberg
2026-08-02 12:48 ` sashiko-bot [this message]
2026-08-02 22:17 ` Uwe Kleine-König
2026-08-02 12:42 ` [PATCH RFC 3/3] arm64: dts: qcom: sdm845-oneplus-fajita: Enable speaker codec David Heidelberg via B4 Relay
2026-08-02 12:42 ` David Heidelberg
2026-08-02 12:55 ` sashiko-bot
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=20260802124855.ABB921F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.