[U-Boot] [EXT] Re: The CONFIG_DM_I2C_COMPAT option is not available

[Chuanhua Han]

hi, Heiko Schocher
> -----Original Message-----
> From: Heiko Schocher <hs at denx.de>
> Sent: 2019年5月17日 11:33
> To: Chuanhua Han <chuanhua.han at nxp.com>
> Cc: U-Boot-Denx <u-boot at lists.denx.de>
> Subject: [EXT] Re: The CONFIG_DM_I2C_COMPAT option is not available
> 
> Caution: EXT Email
> 
> Hello Chuanhua Han,
> 
> Am 16.05.2019 um 13:44 schrieb Chuanhua Han:
> > hi, Heiko Schocher
> >
> > Some soc related files use i2c_read, i2c_write similar function
> > interface,
> >
> > if you do not use the CONFIG_DM_I2C_COMPAT option to compile,
> >
> > there will be a function undefined compilation error,
> 
> For which board, which driver?
> 
> > but if you do CONFIG_DM_I2C_COMPAT=y When compiling,
> >
> > there will be the following warnings:
> >
> > ===================== WARNING ======================
> >
> > This board uses CONFIG_DM_I2C_COMPAT. Please remove
> >
> > (possibly in a subsequent patch in your series)
> >
> > before sending patches to the mailing list.
> >
> > ====================================================
> >
> > If I do ONFIG_DM_I2C_COMPAT=y, do I need to implement i2c_read,
> > i2c_write such as the function interface definition in the i2c controller driver?
> 
> No.
OK,. Thanks for your reply. I am doing dm conversion now
> 
> > But these function declarations are all from include/i2c.h, if
> > CONFIG_DM_I2C=y, these functions are not declared.
> 
> Intentionally.
> 
> > How should I be compatible with these old-style interfaces?
> 
> You should port the parts which break to DM model.
> 
> bye,
> Heiko
> > look forward to your reply!
> >
> > Thanks,
> >
> > Chuanhua
> >
> 
> --
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: hs at denx.de