Linux-i3c Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Arnd Bergmann <arnd@kernel.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Boris Brezillon <bbrezillon@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i3c: fix module_i3c_i2c_driver() with I3C=n
Date: Fri, 25 Jul 2025 09:28:11 -0400	[thread overview]
Message-ID: <aIOGa1ILK9ySlzQS@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <8cf89734-0663-4453-a079-8bdf40625746@roeck-us.net>

On Fri, Jul 25, 2025 at 02:19:19AM -0700, Guenter Roeck wrote:
> On 7/25/25 02:06, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > When CONFIG_I3C is disabled and the i3c_i2c_driver_register() happens
> > to not be inlined, any driver calling it still references the i3c_driver
> > instance, which then causes a link failure:
> >
> > x86_64-linux-ld: drivers/hwmon/lm75.o: in function `lm75_i3c_reg_read':
> > lm75.c:(.text+0xc61): undefined reference to `i3cdev_to_dev'
> > x86_64-linux-ld: lm75.c:(.text+0xd25): undefined reference to `i3c_device_do_priv_xfers'
> > x86_64-linux-ld: lm75.c:(.text+0xdd8): undefined reference to `i3c_device_do_priv_xfers'
> >
> > This issue was part of the original i3c code, but only now caused problems
> > when i3c support got added to lm75.
> >
> > Change the 'inline' annotations in the header to '__always_inline' to
> > ensure that the dead-code-elimination pass in the compiler can optimize
> > it out as intended.
> >
> > Fixes: 6071d10413ff ("hwmon: (lm75) add I3C support for P3T1755")
> > Fixes: 3a379bbcea0a ("i3c: Add core I3C infrastructure")
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Reviewed-by: Frank Li <Frank.Li@nxp.com>

>
> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>
> > ---
> >   include/linux/i3c/device.h | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/linux/i3c/device.h b/include/linux/i3c/device.h
> > index b674f64d0822..7f136de4b73e 100644
> > --- a/include/linux/i3c/device.h
> > +++ b/include/linux/i3c/device.h
> > @@ -245,7 +245,7 @@ void i3c_driver_unregister(struct i3c_driver *drv);
> >    *
> >    * Return: 0 if both registrations succeeds, a negative error code otherwise.
> >    */
> > -static inline int i3c_i2c_driver_register(struct i3c_driver *i3cdrv,
> > +static __always_inline int i3c_i2c_driver_register(struct i3c_driver *i3cdrv,
> >   					  struct i2c_driver *i2cdrv)
> >   {
> >   	int ret;
> > @@ -270,7 +270,7 @@ static inline int i3c_i2c_driver_register(struct i3c_driver *i3cdrv,
> >    * Note that when CONFIG_I3C is not enabled, this function only unregisters the
> >    * @i2cdrv.
> >    */
> > -static inline void i3c_i2c_driver_unregister(struct i3c_driver *i3cdrv,
> > +static __always_inline void i3c_i2c_driver_unregister(struct i3c_driver *i3cdrv,
> >   					     struct i2c_driver *i2cdrv)
> >   {
> >   	if (IS_ENABLED(CONFIG_I3C))
>
>
> --
> linux-i3c mailing list
> linux-i3c@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-i3c

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2025-07-25 13:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  9:06 [PATCH] i3c: fix module_i3c_i2c_driver() with I3C=n Arnd Bergmann
2025-07-25  9:19 ` Guenter Roeck
2025-07-25 13:28   ` Frank Li [this message]
2025-07-30  0:12 ` Randy Dunlap
2025-07-30 23:40 ` Alexandre Belloni

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=aIOGa1ILK9ySlzQS@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=bbrezillon@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=wsa+renesas@sang-engineering.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