From: Ludovic Desroches <ludovic.desroches@microchip.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Juergen Fitschen <me@jue.yt>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [v2,3/3] i2c: at91: added slave mode support
Date: Tue, 10 Jul 2018 10:42:57 +0200 [thread overview]
Message-ID: <20180710084257.ewgnvroow5weffvf@M43218.corp.atmel.com> (raw)
In-Reply-To: <20180709155135.bjwhrmbk6j26fx4c@ninjato>
On Mon, Jul 09, 2018 at 05:51:36PM +0200, Wolfram Sang wrote:
>
> > Sorry for having not catched it. If I remember well, it was the only
> > issue I had while testing the slave support.
> >
> > >
> > > BTW maybe I asked already and forgot: is this IP core capable of being
> > > master and slave on the same bus?
> > >
> >
> > No the master and slave modes are exclusive.
>
> Pity.
>
> But thanks for the heads up, any tag you want to give? Ack or Rev?
>
Yes sure, you can add my Ack. I would be pleased to see the slave
support taken.
Regards
Ludovic
next prev parent reply other threads:[~2018-07-10 8:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 17:21 [PATCH v2 0/3] i2c: at91: " Juergen Fitschen
2017-11-09 17:21 ` [PATCH v2 1/3] i2c: at91: segregate master mode specific code from probe and init func Juergen Fitschen
2017-11-09 17:22 ` [PATCH v2 2/3] i2c: at91: split driver into core and master file Juergen Fitschen
2017-11-09 17:22 ` [PATCH v2 3/3] i2c: at91: added slave mode support Juergen Fitschen
2017-12-03 18:02 ` Ludovic Desroches
2017-12-11 9:25 ` Juergen Fitschen
2018-06-02 21:35 ` [v2,3/3] " Wolfram Sang
2018-07-09 15:15 ` Ludovic Desroches
2018-07-09 15:51 ` Wolfram Sang
2018-07-10 8:42 ` Ludovic Desroches [this message]
2018-07-12 21:48 ` Wolfram Sang
2018-07-12 21:56 ` Wolfram Sang
2018-07-13 6:37 ` Ludovic Desroches
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=20180710084257.ewgnvroow5weffvf@M43218.corp.atmel.com \
--to=ludovic.desroches@microchip.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@jue.yt \
--cc=wsa@the-dreams.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
all inboxes | Powered by JetHome®