From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] i2c: merge all i2c_reg_read() and i2c_reg_write() into inline functions
Date: Mon, 15 Dec 2008 17:42:28 -0600 [thread overview]
Message-ID: <4946EB64.5060900@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.64ksi.0812151525040.22538@home-gw.koi8.net>
ksi at koi8.net wrote:
> On Mon, 15 Dec 2008, Wolfgang Denk wrote:
>
> Are you going to implement support for multiple I2C busses on some boards?
> I'm working on something like this now so it would be nice to coordinate our
> efforts somehow...
Yes, my goal is to add low-level i2c functions that take an i2c bus as a
parameter. So instead of
i2c_set_bus_num(1);
i2c_read(...);
you can do
i2c_read(1, ...)
or something like that. My goal is to eliminate i2c_set_bus_num() and
everything related to it.
It sounds like we're working on something very similar. This is very
low-priority for me, though.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-12-15 23:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 17:28 [U-Boot] [PATCH v3] i2c: merge all i2c_reg_read() and i2c_reg_write() into inline functions Timur Tabi
2008-12-06 17:49 ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-15 22:47 ` Wolfgang Denk
2008-12-15 23:37 ` ksi at koi8.net
2008-12-15 23:42 ` Timur Tabi [this message]
2008-12-16 0:24 ` ksi at koi8.net
2008-12-16 15:19 ` Timur Tabi
2008-12-16 17:58 ` ksi at koi8.net
2008-12-16 18:51 ` Timur Tabi
2008-12-16 19:40 ` ksi at koi8.net
2008-12-16 20:35 ` Jerry Van Baren
2008-12-16 20:58 ` Wolfgang Denk
2008-12-17 3:55 ` ksi at koi8.net
2008-12-16 20:49 ` Wolfgang Denk
2008-12-16 23:46 ` Timur Tabi
2008-12-17 1:00 ` ksi at koi8.net
2008-12-17 1:28 ` Wolfgang Denk
2008-12-16 17:47 ` Scott Wood
2008-12-16 18:07 ` 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=4946EB64.5060900@freescale.com \
--to=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.