From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755137AbcJNICv (ORCPT ); Fri, 14 Oct 2016 04:02:51 -0400 Received: from comal.ext.ti.com ([198.47.26.152]:43259 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751025AbcJNICf (ORCPT ); Fri, 14 Oct 2016 04:02:35 -0400 Subject: Re: [RFC 1/1] drivers: i2c: omap: Add slave support To: Matthijs van Duin , Wolfram Sang References: <20160525141119.14486-1-rk@ti.com> <20160525141119.14486-2-rk@ti.com> <20160825171430.GM2856@katana> CC: Ravikumar Kattekola , Tony Lindgren , "linux-omap@vger.kernel.org" , , lkml From: Ravikumar Message-ID: <0bcfaa15-331d-2838-1dbd-58d1790a3916@ti.com> Date: Fri, 14 Oct 2016 13:33:23 +0530 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Saturday 27 August 2016 07:29 PM, Matthijs van Duin wrote: > Greetings, unfortunate souls trying to use the omap-i2c peripheral in > slave mode! :-) That would be me :( and greetings to you too :) > I recently posted some stuff about exactly that topic on TI's E2E > forum, you may want to read this warning: > http://e2e.ti.com/support/arm/sitara_arm/f/791/p/514961/1955843#1955843 > and post contains suggestions on using slave mode and details on the > peripheral actually behaves: > http://e2e.ti.com/support/arm/sitara_arm/f/791/p/514961/1959417#1959417 Thanks for doing extensive testing on the OMAP I2C and preserving your notes. I really appreciate sharing the detailed notes and workarounds to avoid lockups. I'll following up with the HW team on your observations. > > Matthijs