From: Jens Scharsig <esw@bus-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch] [Version 2] Disable/Enable Flat I²C Commands
Date: Fri, 30 Jan 2009 08:37:34 +0100 [thread overview]
Message-ID: <gluams$7l4$2@ger.gmane.org> (raw)
This is the seconded version of "Disable/Enable Flat I?C Commands"
Patch. It has invert logic, that means a new define disables the flat
command instaed of reenable.
Since CONFIG_I2C_CMD_TREE are defined, the old flat i2c commands are
still present.
This patch disables the old flat command by default, if
both CONFIG_I2C_CMD_TREE and CONFIG_I2C_CMD_FLAT are defined.
The new option CONFIG_I2C_CMD_NO_FLAT makes it possible to dissable the
flat, when tree commands are used.
Signed-off-by: Jens Scharsig <esw@bus-elektronik.de>
---
diff --git a/README b/README
index 86c1304..0568352 100644
--- a/README
+++ b/README
@@ -1306,6 +1306,9 @@ The following options need to be configured:
older 'imm', 'imd', 'iprobe' etc. commands are considered
deprecated and may disappear in the future.
+ CONFIG_I2C_CMD_NO_FLAT enables the old flat i2c commands like
+ 'imm', 'imd', 'iprobe' etc. if CONFIG_I2C_CMD_TREE is defined.
+
CONFIG_HARD_I2C selects a hardware I2C controller.
CONFIG_SOFT_I2C configures u-boot to use a software (aka
diff --git a/common/cmd_i2c.c b/common/cmd_i2c.c
index 16439ac..cf99428 100644
--- a/common/cmd_i2c.c
+++ b/common/cmd_i2c.c
@@ -1324,6 +1324,7 @@ U_BOOT_CMD(
#endif
);
#endif /* CONFIG_I2C_CMD_TREE */
+#if (!defined(CONFIG_I2C_CMD_NO_FLAT) || !defined(CONFIG_I2C_CMD_TREE))
U_BOOT_CMD(
imd, 4, 1, do_i2c_md, \
"i2c memory display", \
@@ -1369,6 +1370,7 @@ U_BOOT_CMD(
"chip address[.0, .1, .2] [# of objects]\n"
" - loop, reading a set of addresses\n"
);
+#endif /* CONFIG_I2C_CMD_FLAT/TREE */
#if defined(CONFIG_CMD_SDRAM)
U_BOOT_CMD(
next reply other threads:[~2009-01-30 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 7:37 Jens Scharsig [this message]
2009-01-30 15:13 ` [U-Boot] [Patch] [Version 2] Disable/Enable Flat I²C Commands Ben Warren
2009-01-30 15:30 ` Jens Scharsig
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='gluams$7l4$2@ger.gmane.org' \
--to=esw@bus-elektronik.de \
--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 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.