[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0bcfaa15-331d-2838-1dbd-58d1790a3916@ti.com>
Date: Fri, 14 Oct 2016 13:33:23 +0530
From: Ravikumar <a0131654@...com>
To: Matthijs van Duin <matthijsvanduin@...il.com>,
Wolfram Sang <wsa@...-dreams.de>
CC: Ravikumar Kattekola <rk@...com>, Tony Lindgren <tony@...mide.com>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
<linux-i2c@...r.kernel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 1/1] drivers: i2c: omap: Add slave support
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
Powered by blists - more mailing lists