From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [for next] i2c, ppc4xx: fix compiling KAREF and METROBOX boards.
Date: Thu, 03 Dec 2009 12:15:52 +0100 [thread overview]
Message-ID: <4B179DE8.2060506@denx.de> (raw)
In-Reply-To: <200912031154.39962.sr@denx.de>
Hello Stefan,
Stefan Roese schrieb:
> On Thursday 03 December 2009 11:23:17 Heiko Schocher wrote:
>> commit eb5eb2b0f744f0cba405160c5d01335c40f09acf
>>
>> ppc4xx: Cleanup PPC4xx I2C infrastructure
>>
>> This patch cleans up the PPC4xx I2C intrastructure:
>>
>> - Use C struct to describe the I2C registers instead of defines
>> - Coding style cleanup (braces, whitespace, comments, line length)
>> - Extract common code from i2c_read() and i2c_write()
>> - Remove unneeded IIC defines from ppc405.h & ppc440.h
>>
>> breaks comiling for the KAREF and METROBOX boards.
>>
>> This patch fixes this issue.
>
> Thanks for catching. Don't know why I missed those two boards.
>
> But looking at the code (board/sandburst/common/ppc440gx_i2c.c), this seems to
> be a driver for the PPC4xx I2C bus 1. The common 4xx I2C driver
> (cpu/ppc4xx/i2c.c) is fully capable of handling I2C bus 0 *and* 1. Perhaps
> this was not the case when Travis wrote the board support. I would really like
> to drop this board specific code, as it doesn't seem necessary for me.
In the multibus_v2 approach I dropped it ;-)
I didn;t see any reasons for supporting this board specific i2c driver
any longer ...
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2009-12-03 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 10:23 [U-Boot] [PATCH] [for next] i2c, ppc4xx: fix compiling KAREF and METROBOX boards Heiko Schocher
2009-12-03 10:54 ` Stefan Roese
2009-12-03 11:15 ` Heiko Schocher [this message]
2009-12-04 22:09 ` Wolfgang Denk
2009-12-05 10:41 ` Heiko Schocher
2009-12-16 8:31 ` Stefan Roese
2009-12-21 9:27 ` Stefan Roese
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=4B179DE8.2060506@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