From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] Bring in new I2C framework
Date: Tue, 30 Oct 2012 15:38:33 -0700 [thread overview]
Message-ID: <20121030223833.GI15024@bill-the-cat> (raw)
In-Reply-To: <508E5206.6060704@denx.de>
On Mon, Oct 29, 2012 at 10:53:10AM +0100, Heiko Schocher wrote:
> Hello Tom,
>
> On 26.10.2012 20:44, Tom Rini wrote:
> >On Thu, Oct 25, 2012 at 02:37:08PM -0700, Simon Glass wrote:
> >
> >[snip]
> >>Later, I wonder whether the concept of a 'current' i2c bus should be
> >>maintained by the command line interpreter, rather than the i2c
> >>system. Because to be honest, most of the drivers I see have to save
> >>the current bus number, set the current bus, do the operation, then
> >>set the bus back how they found it (to preserve whatever the user
> >>things is the current bus).
> >
> >I agree. Lets move the notion of "current" to cmd_i2c and make
> >everything internally pass around the bus to operate on. Or try going
> >down this path and find a fatal problem :)
>
> As I wrote to simon, stephen, this is an independent problem from the
> new framework patches!
OK. I was hoping we could just:
- Change init_func_i2c (for ARM/m68k/ppc/nds32, equiv elsewhere) to init
all configured busses.
- Change the CLI part to track what bus it is operating on.
It sounds like it's more work than just this, really. Since there is
agreement to push things further after this update, yes, OK, we can go
one step at a time here. Thanks!
--
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/20121030/30eda42a/attachment.pgp>
next prev parent reply other threads:[~2012-10-30 22:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 17:40 [U-Boot] [PATCH 0/3] Bring in new I2C framework Heiko Schocher
2012-10-22 17:40 ` [U-Boot] [PATCH 1/3] i2c: add i2c_core and prepare for new multibus support Heiko Schocher
2012-10-22 17:40 ` [U-Boot] [PATCH 2/3] i2c: common changes for multibus/multiadapter support Heiko Schocher
2012-10-22 22:16 ` Henrik Nordström
2012-10-23 3:25 ` Heiko Schocher
2012-10-22 17:40 ` [U-Boot] [PATCH 3/3] i2c, soft-i2c: switch to new " Heiko Schocher
2012-10-25 21:37 ` [U-Boot] [PATCH 0/3] Bring in new I2C framework Simon Glass
2012-10-26 5:48 ` Heiko Schocher
2012-10-26 16:07 ` Stephen Warren
2012-10-29 9:47 ` Heiko Schocher
2012-10-29 15:34 ` Stephen Warren
2012-10-29 15:56 ` Simon Glass
2012-10-30 5:57 ` Heiko Schocher
2012-10-30 16:50 ` Stephen Warren
2012-10-30 17:22 ` Simon Glass
2012-10-31 5:02 ` Heiko Schocher
2012-10-31 5:20 ` Tom Rini
2012-10-26 16:08 ` Simon Glass
2012-10-29 9:44 ` Heiko Schocher
2012-10-29 13:48 ` Simon Glass
2012-10-30 5:44 ` Heiko Schocher
2012-10-26 18:44 ` Tom Rini
2012-10-29 9:53 ` Heiko Schocher
2012-10-30 22:38 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-17 7:12 Simon Glass
2012-01-17 8:30 ` Heiko Schocher
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=20121030223833.GI15024@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