Hi Wolfram, On Tue, Jun 11, 2013 at 08:21:22PM +0200, Wolfram Sang wrote: > The thing is: If there is a bug/errata found in one driver, it goes > unnoticed that it probably should be fixed in the other, too. This is > why sharing logic is a good thing from a maintenance view. Yes, I definitely understand that. > Register offsets are annoying, but one can handle them. There are > examples in the kernel tree. If some registers are totally different > they often can be encapsulated in specific functions processing them. > > So, I'd like to ask you if you can prepare a list of what would be > needed to merge this support into mv64xxx? Then I get a better picture > of what way to go. Can you do this? I had some time to work on this, I sent you the patches. Except for the register offset parts, the logic of the driver itself needed no modifications, so the only "big" change is to pass the register structure somehow. Anyway, I just sent to you the patches I had. Thanks! Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- 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
