From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Fri, 20 Apr 2012 11:48:10 +0200
Subject: [U-Boot] i2c driver for arm926ejs - at91sam9m10g45
In-Reply-To: <CALe7QMDvLtsrSZ5wBYV5y++sVBy1MW=QRh=QAGry+pBNgDJT+w@mail.gmail.com>
References: <CALe7QMDvLtsrSZ5wBYV5y++sVBy1MW=QRh=QAGry+pBNgDJT+w@mail.gmail.com>
Message-ID: <201204201148.10576.marex@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Dear Wilson Perez,

> I'm interested in the i2c driver for the arm926ejs cpu and at91sam9m10g45
> board.  I'm dealing with the issue that when enabling CONFIG_SOFT_I2C it
> needs proper definitions for I2C_INIT, I2C_SDA, I2C_READ, etc. and when
> enabling CONFIG_HARD_I2C the build fails with undefined references:
> i2c_init, i2c_read, i2c_write, i2c_probe.
> 
> Can someone please point me in the right direction?

Well of course, you need to implement that API (i2c_read/write/probe/init() 
calls) if you want hardware-assisted I2c, check your CPU datasheet.

If you implement only soft-spi, you need to implement I2C_SDA etc functions, 
which flip the GPIO lines that emulate the SPI.

> 
> Thanks.
> 
> Wilson

Best regards,
Marek Vasut