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] 0/12 Multiadapter/multibus I2C
Date: Fri, 13 Feb 2009 08:52:45 +0100	[thread overview]
Message-ID: <499526CD.5080206@denx.de> (raw)
In-Reply-To: <Pine.LNX.4.64ksi.0902121345590.21067@home-gw.koi8.net>

Hello ksi,

ksi at koi8.net wrote:
> Here is the second attempt for initial portion of multibus/multiadapter
> I2C support.
>   

Can you please send your patches with some better commit messages.
You only send your Signed-off-by, without any explanation. Please
change this.

> This includes a set of common files, all drivers in drivers/i2c and all
> boards affected by these changes (config files, board files, and lib_xx
> files.)
>
> There is an illustrative example of multiadapter multibus I2C config in
> MPC8548CDS.h config file (#if 0'd.) Definitions in that example are
> bogus so please don't expect it to work. It will compile though...
>
> This set also includes big rework for soft_i2c.c that makes it template
> version that allows up to 4 bitbanged adapters. This number can be
>   

Didn;t you try my suggestion? This is a really big define monster now,
which I think, we can avoid, and without to change nearly all lines of
the existing driver.
> reduced/increased; 4 is arbitrary chosen value. I'm not a CPP guru so I
> did not find a way to make a version without a limit. Sure I could add
> additional configuration variable for this limit but it is one more
> variable and resulting soft_i2c.c would be much uglier.
>
> The general rule for multi-adapter controllers (fsl_i2c, mxc_i2c, etc.)
> is that all defines for the first controller do not have any number in
> their names, the second one has "2" and so on. That allows for
> compatibility with existing code. All existing defaults are kept.
>
> I did test-compile all ARM and PPC boards. Unfortunately I have never
> worked with m68k, mips, blackfin so I don't have toolchains for those
> to do test builds.
>
> The only board that failed to compile was SIMPC8313.h that fails to
> link NAND bootstrap with "NAND bootstrap too big" but it has nothing to
> do with new I2C code; it also fails without my patches.
>
> All patches are against today's u-boot-i2c.git.
>   
bye
Heiko

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

  reply	other threads:[~2009-02-13  7:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 22:09 [U-Boot] [PATCH] 0/12 Multiadapter/multibus I2C ksi at koi8.net
2009-02-13  7:52 ` Heiko Schocher [this message]
2009-02-13 20:15   ` ksi at koi8.net
2009-02-14  8:47     ` Heiko Schocher
2009-02-15  5:51       ` ksi at koi8.net
2009-02-15  8:15         ` Heiko Schocher
2009-02-16  7:46           ` ksi at koi8.net
2009-02-16  9:03             ` Heiko Schocher
2009-02-16 21:31               ` Wolfgang Denk
2009-02-17  5:56                 ` ksi at koi8.net
2009-02-17 12:30                   ` Wolfgang Denk
2009-02-16 21:30             ` Wolfgang Denk
2009-02-17  5:52               ` ksi at koi8.net
2009-02-17 12:27                 ` Wolfgang Denk
2009-02-16 21:13         ` Wolfgang Denk
2009-02-17  5:32           ` ksi at koi8.net
2009-02-17  9:21             ` Heiko Schocher
2009-02-17 12:17             ` Wolfgang Denk
2009-02-16 21:10     ` Wolfgang Denk
2009-02-17  5:23       ` ksi at koi8.net

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=499526CD.5080206@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