Hi Michael, On Mon, 07 Dec 2009 10:07:54 +0100, Michael Lawnick wrote: > on my current project I'm now at the point to have to implement > multiplexer support. The last patch set from Rodolfo was for 2.6.29, Correct. > most parts seem to have been integrated already in 2.6.31 I don't think so, no. What went in (or more exactly, out of) i2c-core in 2.6.31 was the removal of the legacy i2c binding model, along with the cleanups that allowed. It should make multiplexing support easier to add, but that's about it. > If I got it correctly the patch based on creating a mux folder with > i2c-mux.c as a core file and then additional mux layer files. > So my questions: > Rodolfo, do you have a more resent patch set? I've been asking the same some weeks ago. > Jean, what are your plans about multiplexer support, where do you see > open issues? In all honesty, I did not look at Rodolfo's code at all. When he sent it originally, I didn't have the time, being in the middle of major i2c-core changes and cleanups. After 2.6.31 was released, I finally had the time to look into it. But as I knew the recent i2c-core changes would require Rodolfo's patches to be rebased, I asked him to do that first. But now it's apparently Rodolfo's time to be busy :( If you want to help, you're welcome. > Do you agree with current centralized layout or would you > prefer independent single files integrating all necessary parts and > residing in bus folder? Not having looked at the current proposal, I can't really comment on the design. But having a separate folder for mux drivers sounds sane at first sight. -- 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
