Wolfram Sang said the following: > Hi Michael, > >> Can someone give me explanations/links/msg ids? > > Documentation/i2c/upgrading-clients > After re-reading it, I have to state that this document doesn't answer the questions behind my original ones (which I wanted to answer myself by following helpful links): >From which kernel version on should the 'new-binding' model work? How is attaching of a hot plugged i2c device achieved a) from kernel b) from user space. For kernel space init I assume its a call to i2c_new_device(). Here I'm wondering where I should get the adapter info from. For user space I'm completely lost (ioctl on /dev/i2cx?). Our situation: main board is up and running, all drivers loaded. Now an extension board will be plugged in. It is detected by periodically polling via I2C for MUX. After detection the drivers e.g. for temperature an MUX on the secondary board need to be attached to I2C subsystem. Instances of both drivers are already running for local devices, re-loading is only a bad option. Do I really have to read and understand i2c-core.c and i2c-dev.c to find out? -- Michael Lawnick Software Design Engineer Lise-Meitner-Str. 7/1 89081 Ulm Tel: +49 731 9533 2066 Michael.Lawnick.ext@xxxxxxx http://www.nokiasiemensnetworks.com/global/ Think before you print -- 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
