From: Stefan Roese Date: Wed, 28 Mar 2007 12:52:12 +0000 (+0200) Subject: i2c: Enable "old" i2c commands even when CONFIG_I2C_CMD_TREE is defined X-Git-Tag: v1.3.0-rc1~88^2~24 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0c75c9d84307a9f1cbe1ff0c4d8937ee3a96475e;p=kernel%2Fu-boot.git i2c: Enable "old" i2c commands even when CONFIG_I2C_CMD_TREE is defined The "old" i2c commands (iprobe, imd...) are now compiled in again, even when the i2c command tree is enabled via the CONFIG_I2C_CMD_TREE config option. Signed-off-by: Stefan Roese --- diff --git a/common/cmd_i2c.c b/common/cmd_i2c.c index 34571ee..755810d 100644 --- a/common/cmd_i2c.c +++ b/common/cmd_i2c.c @@ -969,7 +969,7 @@ U_BOOT_CMD( "i2c sdram chip - print SDRAM configuration information\n" #endif /* CFG_CMD_SDRAM */ ); -#else /* CONFIG_I2C_CMD_TREE */ +#endif /* CONFIG_I2C_CMD_TREE */ U_BOOT_CMD( imd, 4, 1, do_i2c_md, \ "imd - i2c memory display\n", \ @@ -1024,6 +1024,5 @@ U_BOOT_CMD( " (valid chip values 50..57)\n" ); #endif -#endif /* CONFIG_I2C_CMD_TREE */ #endif /* CFG_CMD_I2C */