From: Tom Rini <trini@konsulko.com>
To: Julien Stephan <jstephan@baylibre.com>
Cc: u-boot@lists.denx.de,
GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>,
Jerome Forissier <jerome.forissier@arm.com>,
"Kory Maincent (TI.com)" <kory.maincent@bootlin.com>,
Simon Glass <sjg@chromium.org>,
Quentin Schulz <quentin.schulz@cherry.de>,
Peter Robinson <pbrobinson@gmail.com>,
Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>,
Heiko Schocher <hs@nabladev.com>,
Andrew Goodbody <andrew.goodbody@linaro.org>
Subject: Re: [PATCH v2] cmd: kconfig: i2c: add missing I2C API dependency
Date: Thu, 2 Jul 2026 10:33:58 -0600 [thread overview]
Message-ID: <20260702163358.GA749385@bill-the-cat> (raw)
In-Reply-To: <20260702-cmd-i2-add-dm-i2c-dependency-v2-1-e048ab426191@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
On Thu, Jul 02, 2026 at 05:26:57PM +0200, Julien Stephan wrote:
> CMD_I2C relies on either the Driver Model I2C API or the legacy I2C
> API, but its Kconfig currently does not enforce either dependency.
>
> As a result, enabling CMD_I2C without DM_I2C or SYS_I2C_LEGACY can lead
> to link errors due to unresolved i2c_* symbols.
>
> Require either DM_I2C or SYS_I2C_LEGACY to prevent unsupported
> configurations while preserving support for legacy platforms.
>
> Signed-off-by: Julien Stephan <jstephan@baylibre.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-07-02 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 15:26 [PATCH v2] cmd: kconfig: i2c: add missing I2C API dependency Julien Stephan
2026-07-02 16:33 ` Tom Rini [this message]
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=20260702163358.GA749385@bill-the-cat \
--to=trini@konsulko.com \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=andrew.goodbody@linaro.org \
--cc=hs@nabladev.com \
--cc=jerome.forissier@arm.com \
--cc=jstephan@baylibre.com \
--cc=kory.maincent@bootlin.com \
--cc=mikhail.kshevetskiy@iopsys.eu \
--cc=pbrobinson@gmail.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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