mfd: max8907c: Do not use I2C_M_NOSTART in first message
authorLaxman Dewangan <ldewangan@nvidia.com>
Thu, 29 Mar 2012 09:54:51 +0000 (14:54 +0530)
committerSimone Willett <swillett@nvidia.com>
Tue, 3 Apr 2012 16:35:50 +0000 (09:35 -0700)
commitb7ce7f54652d73d6fc1f787dfb4aeec3f475a17f
tree24c37a2c463e57bb6b20fa2d9ba9f47e36ba64c4
parent314fcaf5342c1bec21d3d694a30ccdc3d60177cb
mfd: max8907c: Do not use I2C_M_NOSTART in first message

It is not recommended to use the flag I2C_M_NOSTART in first
message.

The documentation kernel/Documentation/i2c/i2c-proocol says:
Flag I2C_M_NOSTART:
    In a combined transaction, no 'S Addr Wr/Rd [A]' is generated at some
    point. For example, setting I2C_M_NOSTART on the second partial message
    generates something like:
      S Addr Rd [A] [Data] NA Data [A] P
    If you set the I2C_M_NOSTART variable for the first partial message,
    we do not generate Addr, but we do generate the startbit S. This will
    probably confuse all other clients on your bus, so don't try this.

Change-Id: I8a8a4f6f91a1b53b6d443588ab18704cf100fd50
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-on: http://git-master/r/93187
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Tested-by: Bandi Krishna Chaitanya <bandik@nvidia.com>
drivers/mfd/max8907c.c