From: Mattijs Korpershoek via U-Boot <u-boot@lists.u-boot-project.org>
To: Anshul Dalal <anshuld@ti.com>, Guo Hao <guohaoprc@163.com>
Cc: "Guillaume La Roque (TI.com)" <glaroque@baylibre.com>,
Mattijs Korpershoek <mkorpershoek@kernel.org>,
u-boot@lists.denx.de, Bryan Brattlof <bb@ti.com>,
Tom Rini <trini@konsulko.com>, Yao Zi <me@ziyao.cc>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Vishal Mahaveer <vishalm@ti.com>, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] board: ti: am62x: Fix build without TI_I2C_BOARD_DETECT
Date: Tue, 21 Jul 2026 10:14:08 +0200 [thread overview]
Message-ID: <87a4rkkbe7.fsf@kernel.org> (raw)
In-Reply-To: <178418750029.393743.12900440415467707713.b4-review@b4>
On Thu, Jul 16, 2026 at 13:08, Anshul Dalal <anshuld@ti.com> wrote:
> On Wed, 15 Jul 2026 11:32:26 +0800, Guo Hao <guohaoprc@163.com> wrote:
>> setup_board_eeprom_env() and setup_serial_am6() are only available when
>> TI_I2C_BOARD_DETECT is enabled.
>>
>> IS_ENABLED() does not remove the guarded statements during preprocessing,
>> so disabling TI_I2C_BOARD_DETECT results in an implicit function
>> declaration error. Use a preprocessor condition to match the condition
>> used for the function definition.
>>
>> Fixes: ff1b83c095c2 ("board: am62x: Add support for reading eeprom data")
>> Signed-off-by: Guo Hao <guohaoprc@163.com>
>
> This is a valid fix however I wonder if there's an actual use-case where someone
> might want to disable TI_I2C_BOARD_DETECT on an EVM board.
I agree with Anshul here. What's the use use-case for disabling i2c
board detection?
Also, if we really want it disabled, we could also create stub functions
instead of replacing this.
>
> Also, it looks like the same issue exists for other platforms too (AM64x, AM65x,
> J721s2 ...).
>
> --
> Anshul Dalal <anshuld@ti.com>
next prev parent reply other threads:[~2026-07-21 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 3:32 [PATCH] board: ti: am62x: Fix build without TI_I2C_BOARD_DETECT Guo Hao
2026-07-15 3:32 ` Guo Hao via B4 Relay
2026-07-15 5:44 ` Varadarajan Narayanan
2026-07-16 7:38 ` Anshul Dalal
2026-07-21 8:14 ` Mattijs Korpershoek via U-Boot [this message]
[not found] ` <7b7be0c1.8185.19f841a7a0c.Coremail.guohaoprc@163.com>
2026-07-21 14:14 ` Mattijs Korpershoek via U-Boot
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=87a4rkkbe7.fsf@kernel.org \
--to=u-boot@lists.u-boot-project.org \
--cc=anshuld@ti.com \
--cc=bb@ti.com \
--cc=glaroque@baylibre.com \
--cc=guohaoprc@163.com \
--cc=me@ziyao.cc \
--cc=mkorpershoek@kernel.org \
--cc=patrice.chotard@foss.st.com \
--cc=peng.fan@nxp.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vishalm@ti.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 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.