public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] drivers/designware_i2c - add suppor of CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW
Date: Fri, 17 Jan 2014 07:42:20 +0100	[thread overview]
Message-ID: <52D8D0CC.8000402@denx.de> (raw)
In-Reply-To: <1389800264.19230.18.camel@abrodkin-8560l>

Hello Alexey,

Am 15.01.2014 16:37, schrieb Alexey Brodkin:
> On Mon, 2013-12-16 at 15:30 +0400, Alexey Brodkin wrote:
>> Since we agreed on legacy implementation of "eeprom_{read|write}"
>> (http://patchwork.ozlabs.org/patch/295825/) I had to fix/make it work
>> again DesignWare I2C driver for cases when 1 EEPROM IC fake I2C with
>> anumber of "built-in" ICs with different chip addresses.
>
> Hi Heiko,
>
> any chance to get this one applied?

I picked it up, see:

http://git.denx.de/?p=u-boot/u-boot-i2c.git;a=summary
http://git.denx.de/?p=u-boot/u-boot-i2c.git;a=commit;h=32d041e218c6a22e92d91629902fd03a90934b6a

> Note this is not an enhancement - this is a required fix due to
> roll-back (http://patchwork.ozlabs.org/patch/295825/) of my previous fix
> in http://patchwork.ozlabs.org/patch/289346/

Waiting for a testreport for another patch ... If I get no response,
I send a pull request for this patch tomorrow ...

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2014-01-17  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 11:30 [U-Boot] [PATCH] drivers/designware_i2c - add suppor of CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW Alexey Brodkin
2014-01-15 15:37 ` Alexey Brodkin
2014-01-17  6:42   ` Heiko Schocher [this message]
2014-01-17  7:44     ` Alexey Brodkin

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=52D8D0CC.8000402@denx.de \
    --to=hs@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox