From: sashiko-bot@kernel.org
To: "James Calligeros" <jcalligeros99@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 10/21] arm64: dts: apple: t8103-j274: Add speaker/headset jack nodes
Date: Sun, 04 Oct 2026 06:17:39 +0000 [thread overview]
Message-ID: <20261004061740.022061F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261004-macaudio-v2-10-7b47ed6335a8@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] dts: codec ti,tas5770l is unprobeable due to missing driver binding
- [Low] dts: duplicate &i2c2 node definition
--
commit 880aa6b0e6df0b9fa5a017a1a3c706d5c89c5508
Author: James Calligeros <jcalligeros99@gmail.com>
arm64: dts: apple: t8103-j274: Add speaker/headset jack nodes
This commit adds speaker and headset jack nodes for the M1 Mac mini. It
integrates Apple-specific variants of the TI TAS2770 and Cirrus CS42L42 by
advertising them to the machine driver via the sound node.
> diff --git a/arch/arm64/boot/dts/apple/t8103-j274.dts b/arch/arm64/boot/dts/apple/t8103-j274.dts
> --- a/arch/arm64/boot/dts/apple/t8103-j274.dts
> +++ b/arch/arm64/boot/dts/apple/t8103-j274.dts
> @@ -75,4 +75,71 @@ &i2c2 {
> status = "okay";
> };
>
> +/* Audio codecs */
> +&i2c1 {
> + status = "okay";
> +
> + speaker: codec@31 {
> + compatible = "ti,tas5770l";
[Severity: High]
Will this codec successfully probe? The intended codec driver's match table
in sound/soc/codecs/tas2770.c does not appear to include this compatible
string:
sound/soc/codecs/tas2770.c:tas2770_of_match[] {
{ .compatible = "ti,tas2770" },
{},
};
Without a matching driver binding or a generic fallback string like
"ti,tas2770" in the DTS, the kernel's I2C core and OF matching will fail
to bind a driver. Does this leave the codec component permanently in
deferred probe and prevent the sound card from initializing?
> + reg = <0x31>;
> + interrupts-extended = <&pinctrl_ap 182 IRQ_TYPE_LEVEL_LOW>;
[ ... ]
> + };
> +};
> +
> +&i2c2 {
[Severity: Low]
Does this file already have an &i2c2 node defined right above this hunk?
While the Device Tree Compiler safely merges duplicate nodes into a single
block during compilation, is it preferred to nest the new jack_codec node
inside the existing &i2c2 block to avoid redundant top-level references?
> + status = "okay";
> +
> + jack_codec: codec@48 {
> + compatible = "cirrus,cs42l83";
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261004-macaudio-v2-0-7b47ed6335a8@gmail.com?part=10
next prev parent reply other threads:[~2026-10-04 6:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 6:03 [PATCH v2 00/21] Add speaker and headset jack support for Apple Silicon Macs James Calligeros
2026-10-04 6:03 ` [PATCH v2 01/21] ASoC: dt-bindings: cs42l84: Document sound-name-prefix property James Calligeros
2026-10-04 6:03 ` [PATCH v2 02/21] ASoC: dt-bindings: cs42l42: Do not require chip power supplies James Calligeros
2026-10-04 6:03 ` [PATCH v2 03/21] ASoC: dt-bindings: cs42l42: Document #sound-dai-cells property James Calligeros
2026-10-04 6:03 ` [PATCH v2 04/21] ASoC: dt-bindings: cs42l42: Document sound-name-prefix property James Calligeros
2026-10-04 6:03 ` [PATCH v2 05/21] ASoC: dt-bindings: Add binding for Apple Silicon Mac audio James Calligeros
2026-10-04 6:15 ` sashiko-bot
2026-10-04 6:03 ` [PATCH v2 06/21] ASoC: ops: Introduce 'snd_soc_deactivate_kctl' James Calligeros
2026-10-04 6:03 ` [PATCH v2 07/21] ASoC: ops: Introduce 'soc_set_enum_kctl' James Calligeros
2026-10-04 6:22 ` sashiko-bot
2026-10-07 17:36 ` Ajay Kumar Nandam
2026-10-04 6:03 ` [PATCH v2 08/21] ASoC: card: Let 'fixup_controls' return errors James Calligeros
2026-10-07 14:23 ` Charles Keepax
2026-10-04 6:03 ` [PATCH v2 09/21] ASoC: apple: Add macaudio machine driver James Calligeros
2026-10-04 6:24 ` sashiko-bot
2026-10-07 18:04 ` Ajay Kumar Nandam
2026-10-04 6:03 ` [PATCH v2 10/21] arm64: dts: apple: t8103-j274: Add speaker/headset jack nodes James Calligeros
2026-10-04 6:17 ` sashiko-bot [this message]
2026-10-07 18:17 ` Ajay Kumar Nandam
2026-10-04 6:03 ` [PATCH v2 11/21] arm64: dts: apple: t8103-j313: " James Calligeros
2026-10-04 6:19 ` sashiko-bot
2026-10-07 18:32 ` Ajay Kumar Nandam
2026-10-08 8:46 ` James Calligeros
2026-10-08 9:34 ` Ajay Kumar Nandam
2026-10-04 6:03 ` [PATCH v2 12/21] arm64: dts: apple: t8103-j293: " James Calligeros
2026-10-04 6:25 ` sashiko-bot
2026-10-04 6:03 ` [PATCH v2 13/21] arm64: dts: apple: t8103-j45x: Add headset " James Calligeros
2026-10-04 6:21 ` sashiko-bot
2026-10-08 6:18 ` Ajay Kumar Nandam
2026-10-04 6:03 ` [PATCH v2 14/21] arm64: dts: apple: t8112-j413: Add speaker/headset " James Calligeros
2026-10-04 6:03 ` [PATCH v2 15/21] arm64: dts: apple: t8112-j415: " James Calligeros
2026-10-04 6:21 ` sashiko-bot
2026-10-04 6:03 ` [PATCH v2 16/21] arm64: dts: apple: t8112-j473: " James Calligeros
2026-10-04 6:03 ` [PATCH v2 17/21] arm64: dts: apple: t8112-j493: " James Calligeros
2026-10-04 6:03 ` [PATCH v2 18/21] arm64: dts: apple: t600x-j31x: " James Calligeros
2026-10-04 6:24 ` sashiko-bot
2026-10-04 6:03 ` [PATCH v2 19/21] arm64: dts: apple: t600x-j375: " James Calligeros
2026-10-04 6:03 ` [PATCH v2 20/21] arm64: dts: apple: t602x-j41x: " James Calligeros
2026-10-04 6:03 ` [PATCH v2 21/21] arm64: dts: apple: t602x-j47x: " James Calligeros
2026-10-08 9:29 ` Ajay Kumar Nandam
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=20261004061740.022061F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jcalligeros99@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox