From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Revert "common, env: Fix support for environment in i2c eeprom"
Date: Tue, 14 Oct 2014 16:21:29 +0200 [thread overview]
Message-ID: <543D3169.4010505@keymile.com> (raw)
In-Reply-To: <543D17D3.608@esd.eu>
Hi Matthias,
On 10/14/2014 02:32 PM, Matthias Fuchs wrote:
> Hi Valentin,
>
> my patch fixed environment from i2c eeprom. I am not sure on which board
> I ran into that trouble. Probably PMC440. So reverting my former patch
> will break environment in i2c eeprom again on many boards.
Good that you have answered to patch. I run into that trouble on our Keymile
boards that have the environment in the EEPROM. On our boards, the environment
eeprom works with or without your patch. However, with your patch, I cannot
directly access ANY eeprom which is not on the CONFIG_I2C_ENV_EEPROM_BUS bus.
>
> But perhaps there's a better way to fix that.
I think that the proposal that Holger made to actually define
CONFIG_I2C_ENV_EEPROM_BUS for your boards is what I would try first.
Valentin
>
> Matthias
>
>
> On 10/14/2014 11:16 AM, Valentin Longchamp wrote:
>> Since i2c_init_all always sets the bus back to CONFIG_SYS_SPD_BUS_NUM
>> for compatibility reasons, it means that any eeprom not located on this
>> CONFIG_SYS_SPD_BUS_NUM is not accessible with the eeprom commands, even
>> if you change the bus number with an i2c dev command before.
>>
>> Furthermore i2c_init_all should disappear and is currently only called
>> from the early board initialisation sequences, it is not suited for
>> other usage.
>>
>> This reverts commit 01a0c64762e902971b34587a8a61b59e9ea51374.
>>
>> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
>>
>> ---
>>
>> common/cmd_eeprom.c | 9 ++-------
>> 1 file changed, 2 insertions(+), 7 deletions(-)
>>
>> diff --git a/common/cmd_eeprom.c b/common/cmd_eeprom.c
>> index a02f0cb..29f0f1f 100644
>> --- a/common/cmd_eeprom.c
>> +++ b/common/cmd_eeprom.c
>> @@ -389,13 +389,8 @@ void eeprom_init (void)
>> #if defined(CONFIG_SPI) && !defined(CONFIG_ENV_EEPROM_IS_ON_I2C)
>> spi_init_f ();
>> #endif
>> -#if defined(CONFIG_HARD_I2C) || defined(CONFIG_SYS_I2C_SOFT) || \
>> - defined(CONFIG_SYS_I2C)
>> -#ifdef CONFIG_SYS_I2C
>> - i2c_init_all();
>> -#else
>> - i2c_init(CONFIG_SYS_I2C_SPEED, CONFIG_SYS_I2C_SLAVE);
>> -#endif
>> +#if defined(CONFIG_HARD_I2C) || defined(CONFIG_SYS_I2C_SOFT)
>> + i2c_init (CONFIG_SYS_I2C_SPEED, CONFIG_SYS_I2C_SLAVE);
>> #endif
>> }
>>
>>
>
>
next prev parent reply other threads:[~2014-10-14 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 9:16 [U-Boot] [PATCH] Revert "common, env: Fix support for environment in i2c eeprom" Valentin Longchamp
2014-10-14 12:32 ` Matthias Fuchs
2014-10-14 13:01 ` Holger Brunck
2014-10-14 14:20 ` Matthias Fuchs
2014-10-14 14:21 ` Valentin Longchamp [this message]
2014-10-23 14:15 ` Matthias Fuchs
2014-10-23 15:11 ` Tom Rini
2014-10-23 15:29 ` Matthias Fuchs
2014-10-27 22:19 ` [U-Boot] " Tom Rini
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=543D3169.4010505@keymile.com \
--to=valentin.longchamp@keymile.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox