From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yegor Yefremov Subject: Re: OMAP: send i2c message ignoring NAK Date: Thu, 19 Jul 2012 15:05:21 +0200 Message-ID: References: <20120703103221.62fcb7ae@endymion.delvare> <4FFDAF5A.8070205@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Shubhrajyoti Datta Cc: "Datta, Shubhrajyoti" , Jean Delvare , Linux I2C List-Id: linux-i2c@vger.kernel.org On Tue, Jul 17, 2012 at 4:01 PM, Shubhrajyoti Datta wrote: > On Tue, Jul 17, 2012 at 3:01 PM, Yegor Yefremov > wrote: >> On Thu, Jul 12, 2012 at 7:24 AM, Datta, Shubhrajyoti >> wrote: > [...] >>> On Wed, Jul 11, 2012 at 10:22 PM, Shubhrajyoti wrote: > > >> >> Thank you for the patch and sorry for delay. I tried the patch, > > Thanks for the test. > >> but it doesn't help. I still get timeouts only. I fear it is really a >> hardware feature, > > I feel that could be unlikely. > >> that OMAPs i2c stops if address is not acknowledged. >> At least this is my understanding of the reference manual. >> >> Here is the output from dmesg: > > > Another request. Can you disable the NACK interrupt on the ignore and > enable back? > > Also let me know if you know of any of the panda or sdp peripherals > which could keep going on > NACK. I don't know any :-( This is also a not very common hardware where you have to make such tricks. > patch below. As I understand it is a stand alone patch not based on the previous one? I have the same result - timeout. Yegor