From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Jagan Teki <jagannadh.teki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: I2C Slave monitor mode support
Date: Tue, 17 Jun 2014 14:19:12 +0200 [thread overview]
Message-ID: <20140617121912.GA2683@katana> (raw)
In-Reply-To: <CAD6G_RRa9C0umBrR6CUF3zb5cSKKfZO7y7UPUKHjJOx41A0aJQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
> Few of the I2C interfaces are [operated] with slave monitor mode, when
> there is a requirement for
> a particular slave may need to wait some time to get the ADDR before
> sending an ACK.
Can you describe an existing scenario? Why can't the slave use clock
stretching?
> This feature is an optional and defined in few of the controllers, Can
> anyone tell me is this support is
> added already in kernel, if yes please point to the respective driver
> or code link.
None that I know of. The above questions should help me understand why
it is needed on master driver level at all.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-17 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 9:57 I2C Slave monitor mode support Jagan Teki
[not found] ` <CAD6G_RRa9C0umBrR6CUF3zb5cSKKfZO7y7UPUKHjJOx41A0aJQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-17 12:19 ` Wolfram Sang [this message]
[not found] ` <CAOZ77ogXPwXPtUxROJKT2wX=2wkZeHeWPZaBhyCnoP0zMxi8mw@mail.gmail.com>
[not found] ` <CAOZ77ogXPwXPtUxROJKT2wX=2wkZeHeWPZaBhyCnoP0zMxi8mw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-18 12:35 ` Wolfram Sang
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=20140617121912.GA2683@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=jagannadh.teki-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).