From: Wolfram Sang <wsa@the-dreams.de>
To: Matthijs van Duin <matthijsvanduin@gmail.com>
Cc: Ravikumar Kattekola <rk@ti.com>, Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-i2c@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC 1/1] drivers: i2c: omap: Add slave support
Date: Sat, 27 Aug 2016 19:22:12 +0200 [thread overview]
Message-ID: <20160827172211.GA1601@katana> (raw)
In-Reply-To: <CAALWOA-XP+mfTcVPc1LZZofAaCK-KtKhFKKKHu2PyHWFrfir3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
> Greetings, unfortunate souls trying to use the omap-i2c peripheral in
> slave mode! :-)
Uh, that sounds like bad HW...
> 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
While it surely is nice to have super detailed information, can you give
this overloaded maintainer a few-line, high level summary of what is
written there?
Thanks,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-27 17:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 14:11 [RFC 0/1] i2c: omap: Add support for switching to slave mode Ravikumar Kattekola
2016-05-25 14:11 ` [RFC 1/1] drivers: i2c: omap: Add slave support Ravikumar Kattekola
2016-05-26 16:07 ` Manish Badarkhe
2016-08-25 17:14 ` Wolfram Sang
2016-08-27 13:59 ` Matthijs van Duin
2016-08-27 17:22 ` Wolfram Sang [this message]
2016-08-27 23:38 ` Matthijs van Duin
2016-08-28 5:35 ` Wolfram Sang
2016-08-29 3:43 ` Matthijs van Duin
2016-10-14 8:57 ` Ravikumar
2016-10-17 6:15 ` Matthijs van Duin
2016-10-14 8:03 ` Ravikumar
2016-10-14 7:56 ` Ravikumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160827172211.GA1601@katana \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=matthijsvanduin@gmail.com \
--cc=rk@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).