On Tue, Jan 19, 2016 at 03:32:43PM +0530, Sricharan R wrote:
> The definition of i2c_msg says that
>
> "If this is the last message in a group, it is followed by a STOP.
> Otherwise it is followed by the next @i2c_msg transaction segment,
> beginning with a (repeated) START"
>
> So the expectatio
rg; linux-arm-
> m...@vger.kernel.org; ntel...@codeaurora.org; ga...@codeaurora.org;
> linux-kernel@vger.kernel.org; andy.gr...@linaro.org; linux-
> i...@vger.kernel.org; iiva...@mm-sol.com; agr...@codeaurora.org;
> dmaeng...@vger.kernel.org; linux-arm-ker...@lists.infradead.org
> Subject: Re: [PATC
Hi,
> Ah, so what I meant above is there is no 'STOP' bit between each msg in
> i2c_msgs,
> but 'REAPEATED_START' still holds true. We are sending 'START' bit for each
> msg.
> So these is how each msg in i2c_msg is sent,
>
> |--MSG1|-MSG2-|--MSG3|
>
> |S
el.org; linux-
> i...@vger.kernel.org; iiva...@mm-sol.com; ga...@codeaurora.org;
> dmaeng...@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
> andy.gr...@linaro.org; ntel...@codeaurora.org; arch...@codeaurora.org
> Subject: Re: [PATCH V7 3/6] i2c: qup: Transfer each i2c_msg in i2c_msgs
> witho
Hi,
> "If this is the last message in a group, it is followed by a STOP.
> Otherwise it is followed by the next @i2c_msg transaction segment,
> beginning with a (repeated) START"
This is correct.
> So the expectation is that there is no 'STOP' bit inbetween individual
> i2c_msg segments with rep
5 matches
Mail list logo
