Messages in this thread | | | Date | Fri, 18 May 2012 11:52:41 +0530 | Subject | Re: [PATCH 4/8] i2c: i2c-bfin-twi: Tighten condition when failing I2C transfer if MEN bit is reset unexpectedly. | From | Shubhrajyoti Datta <> |
| |
On Fri, May 18, 2012 at 8:11 AM, Zhang, Sonic <Sonic.Zhang@analog.com> wrote: > > >>-----Original Message----- >>From: Shubhrajyoti Datta [mailto:omaplinuxkernel@gmail.com] >>Sent: Thursday, May 17, 2012 7:31 PM >>To: Zhang, Sonic >>Cc: Ben Dooks; Wolfram Sang; linux-i2c@vger.kernel.org; LKML; uclinux-dist- >>devel@blackfin.uclinux.org >>Subject: Re: [PATCH 4/8] i2c: i2c-bfin-twi: Tighten condition when failing I2C >>transfer if MEN bit is reset unexpectedly. >> >>On Wed, May 16, 2012 at 12:50 PM, <sonic.zhang@analog.com> wrote: >>> From: Sonic Zhang <sonic.zhang@analog.com> >>> >>> Correct I2C transfer may fail because interrupt status bits XMTSERV and >>> RCVSERV are not checked when MCOMP interrupt is handled. >>> >>Could you expand MCOMP? > > Master transfer complete (MCOMP) > [1] The initiated master transfer has completed. In the absence of a > repeat start, the bus has been released. > [0] The completion of a transfer has not been detected. >
A trivial suggestion may be the changelog could be enhanced. Thanks for the explanation.
> > Regards, > > Sonic > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |