Hi, On Fri, Jun 29, 2012 at 03:18:32PM +0200, Jean Delvare wrote: > On Fri, 29 Jun 2012 18:42:08 +0530, Shubhrajyoti wrote: > > On Friday 29 June 2012 06:27 PM, Jean Delvare wrote: > > > drivers/gpu/drm/nouveau/nouveau_bios.c:3535:3: warning: (near initialization for ‘msg[1].actual’) [enabled by default] > > > > > > This needs to be all fixed (converted to C99-style struct > > > initialization) before your patch is considered for inclusion. And > > > there may be more that my config did not spot. > > Yes,agree. > > > > The idea of this patch was if the idea is agreed upon then. > > then fixing all the callers could be worked on. > > This is worth fixing anyway, C99-style initialization is always good to > move to. > > > However do you agree with this approach? > > Well you've seen the caveats I mentioned, this will be no easy ride. If > you are willing to take the risk, spend the time documenting the > change, and help people if there are issues, then I'm OK. At least as > long as someone else doesn't come saying it's a very bad idea ;) This approach is a hard-requirement for devices which will pose any interface/feedback with user. We have been working with a piezo driver from TI (drv2665) and it will be used (in most cases at least) to give the user a feedback based on e.g. touchscreen event. Imagine drv2665 responds with a NAK while we're in the middle of driving a wave through it (keep in mind a wave could take seconds to finish, depending on the usecase), if we don't have a way to tell users that we have writen X bytes, how should we make sure to continue driving the wave from the exact byte where we got a NAK ? If can't make sure that detail is true, then such usecases (as piezo drivers) will never work. Another approach would be to not add any field to struct i2c_msg but instead return either the amount of bytes transferred, or an error case. This would mean a series that would: 1) fix all users of struct i2c_master_send() and the like to check for errors as if (ret < 0) instead of if (ret); 2) fix all i2c buses to return the amount of bytes written instead of zero or error case 3) fix Documentation to state that we're now returning the amount of bytes, instead of zero or errno. I'm not sure what will have minimum impact to userland, though. What do you say Jean ? What would you prefer ? -- balbi
Attachment:
signature.asc
Description: Digital signature
