On Thu, 7 Apr 2011 09:00:43 +0100, Mark Brown wrote: > On Thu, Apr 07, 2011 at 09:55:13AM +0200, Jean Delvare wrote: > > On Thu, 7 Apr 2011 07:31:24 +0900, Mark Brown wrote: > > > > You definitely don't know *anything* about the relationships for I2C, > > > especially in embedded systems. > > > Can you please elaborate? The i2c subsystem uses a standard > > parent-children relationship. It seems fairly similar to USB for > > example. The only special case I can think of is with bus multiplexing, > > but it would be easy enough to switch off async suspend/resume in this > > case. > > For I2C itself that's the case but for power and GPIO (which are very > common in conjunction with I2C in the embedded context) we loose the > tree. This is much less of an issue with buses like PCI where > everything is bundled into the bus. Out of curiosity, how is this handled in the synchronous suspend/resume case? -- Jean Delvare -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
