Just a quick note - will start next week on it. Cheers, Bastian 2014-05-21 13:00 GMT+02:00 Wolfram Sang <wsa@xxxxxxxxxxxxx>: > On Thu, Feb 21, 2013 at 08:54:06AM -0600, Bastian Hecht wrote: >> Hi Wolfram, >> >> oh yes I can gladly do so. To make a realistic estimation it might >> take a few weeks until I find time for it though. If we can wait so >> long, count on me. > > Ping. Still interested? > >> >> Best, >> >> Bastian >> >> 2013/2/21 Wolfram Sang <wsa@xxxxxxxxxxxxx>: >> > Hi Bastian, >> > >> >> > Also, do you know the reason why this isn't handled in the i2c layer >> >> > by default? I ask because your comment mentions that i2c-tegra.c does >> >> > the same thing and I can't see anything in this patch that is actually >> >> > related to our I2C hardware. >> >> >> >> Yes, many drivers have a similar scheme and to me it more looked like >> >> all drivers need to take care about this case unrelated to different >> >> hardware. So the question arises if this can't be handled in the core >> >> - or if I get something wrong here. >> > >> > I don't see any reason why this couldn't be handled in the core. If you >> > want to have a take on this issue (after the other bug is fixed), this >> > will be highly appreciated. >> > >> > Thanks, >> > >> > Wolfram >> > -- 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
