From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] i2c, omap24xx: convert driver to new mutlibus/mutliadapter framework
Date: Fri, 30 Aug 2013 14:55:56 -0400 [thread overview]
Message-ID: <20130830185556.GU17898@bill-the-cat> (raw)
In-Reply-To: <52202340.5020100@denx.de>
On Fri, Aug 30, 2013 at 06:44:48AM +0200, Heiko Schocher wrote:
> Hello Tom,
>
> Am 29.08.2013 16:05, schrieb Tom Rini:
> >On Mon, Aug 19, 2013 at 04:48:04PM +0200, Heiko Schocher wrote:
> >
> >>- add omap24xx driver to new multibus/multiadpater support
> >>- adapted all config files, which uses this driver
> >>
> >>Tested on the am335x based siemens boards rut, dxr2 and pxm2
> >>posted here:
> >>http://patchwork.ozlabs.org/patch/263211/
> >
> >On top of current master, on omap3_beagle (xM):
> >U-Boot SPL 2013.10-rc1-00054-g03028ca (Aug 29 2013 - 09:46:45)
> >Error, wrong i2c adapter 0 max 0 possible
> >Error, wrong i2c adapter 0 max 0 possible
> >... hang here ...
>
> :-(
>
> It seems there is no i2c adapter ... I just tried to rebase this
> patch against current u-boot-ti and get a merge error in
>
> include/configs/ti_armv7_common.h
>
> So, I repost a v3 of this patch against u-boot-ti commit
> 901ce27c6f018992b7dd6c08d3c98cf217cc4c96 where the siemens boards
> are added. Can you have a look at this new patch?
>
> With this patch on current u-boot-ti I find three i2c adapters
> in U-Boot (System.map):
>
> 8014afe4 D _u_boot_list_2_i2c_2_omap24_0
> 8014afe4 d end.6414
> 8014afe4 d start.6364
> 8014afe4 d start.6368
> 8014afe4 d start.6389
> 8014afe4 d start.6412
> 8014afe4 d start.6800
> 8014afe4 d start.6811
> 8014afe4 d start.6827
> 8014b00c D _u_boot_list_2_i2c_2_omap24_1
> 8014b034 D _u_boot_list_2_i2c_2_omap24_2
> 8014b05c B __bss_base
>
> and three adapter in spl code (spl/u-boot-spl.map):
>
> .data 0x00000000 0x0 drivers/i2c/libi2c.o
> .u_boot_list_2_i2c_2_omap24_0
> 0x00000000 0x28 drivers/i2c/libi2c.o
> .u_boot_list_2_i2c_2_omap24_1
> 0x00000000 0x28 drivers/i2c/libi2c.o
> .u_boot_list_2_i2c_2_omap24_2
> 0x00000000 0x28 drivers/i2c/libi2c.o
> .bss 0x00000000 0x0 drivers/i2c/libi2c.o
Ah-ha! These are in the discard section of the map, which is why v3
still fails.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130830/84b0e2c8/attachment.pgp>
prev parent reply other threads:[~2013-08-30 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 4:58 [U-Boot] [PATCH] i2c, omap24xx: convert driver to new mutlibus/mutliadapter framework Heiko Schocher
[not found] ` <520774D5.7010106@compulab.co.il>
2013-08-13 6:47 ` Nikita Kiryanov
2013-08-19 14:48 ` [U-Boot] [PATCH v2 1/2] " Heiko Schocher
2013-08-29 14:05 ` Tom Rini
2013-08-30 4:44 ` Heiko Schocher
2013-08-30 12:35 ` Tom Rini
2013-08-30 18:55 ` Tom Rini [this message]
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=20130830185556.GU17898@bill-the-cat \
--to=trini@ti.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