From: Juergen Fitschen <me@jue.yt>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-i2c@vger.kernel.org
Subject: Re: I2C slave mode for i2c-at91 driver
Date: Wed, 18 Oct 2017 14:40:54 +0200 [thread overview]
Message-ID: <e63b922a43905f912262652ff888e02f@jfitschen.de> (raw)
In-Reply-To: <20171018073115.ewuoy5z3pbrysx4i@pengutronix.de>
Hi Uwe,
> <halfknowledge> Isn't the at91 i2c hardware broken or unreliable such
> that it's usually recommended to stick to i2c-gpio? If so maybe the
> same
> applies to client mode and someone should better extend i2c-gpio to
> handle the slave API?
Can you describe what kind of unreliability you've observed? I had the
master and slave mode running for some time and it seems to work quite
well. No data losses. No undesired states.
Best regards,
Juergen
next prev parent reply other threads:[~2017-10-18 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 10:56 I2C slave mode for i2c-at91 driver Juergen Fitschen
2017-10-18 7:31 ` Uwe Kleine-König
2017-10-18 7:43 ` Wolfram Sang
2017-10-18 8:00 ` Uwe Kleine-König
2017-10-18 12:40 ` Juergen Fitschen [this message]
2017-10-18 7:37 ` Wolfram Sang
2017-10-18 12:32 ` Juergen Fitschen
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=e63b922a43905f912262652ff888e02f@jfitschen.de \
--to=me@jue.yt \
--cc=linux-i2c@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).