public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] i2c driver for arm926ejs - at91sam9m10g45
Date: Fri, 20 Apr 2012 11:48:10 +0200	[thread overview]
Message-ID: <201204201148.10576.marex@denx.de> (raw)
In-Reply-To: <CALe7QMDvLtsrSZ5wBYV5y++sVBy1MW=QRh=QAGry+pBNgDJT+w@mail.gmail.com>

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

      reply	other threads:[~2012-04-20  9:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 15:08 [U-Boot] i2c driver for arm926ejs - at91sam9m10g45 Wilson Perez
2012-04-20  9:48 ` Marek Vasut [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=201204201148.10576.marex@denx.de \
    --to=marex@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