[U-Boot] [PATCH] 7/12 Multiadapter/multibus I2C, drivers part 4

[Wolfgang Denk]

Dear ksi at koi8.net,

In message <Pine.LNX.4.64ksi.0902181602470.6072 at home-gw.koi8.net> you wrote:
> 
> > Good question. Probably each  I2C  device  will  have  some  list  of
> > bus/adapter  ID's  that need to be up to access it, and that will get
> > shut down afterwards.
> 
> Eh, that is what I call overcomplicated... And it definitely does not belong
> to I2C subsystem per se, it's up to the board developer to know which bus

You want to support complex systems, so let's assume this: The  board
developer  may  not know this. He designs a board which runs some I2C
signals to some connectors where other boards, unknown to him may  or
may  not  be  connected.  Only the system integrator plugs together a
system and knows the bus topology and where which device is.

> each device is connected to. I2C system can not now where that "afterwards"
> happen. If we are reading something from a device, checking some bit,
> writing something else back depending on that bit and then repeat the entire
> cycle (let's say we are polling for something and until that something
> happened we are sending a "please continue" command back to that device,
> then we tell it "thanks, stop now",) where in this sequence that
> "afterwards" happens?

After your last question mark.


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
All easy problems have already been solved.