From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: cadence: Handling Slave monitor mode
Date: Fri, 27 Mar 2015 16:37:13 +0100 [thread overview]
Message-ID: <20150327153713.GC27238@katana> (raw)
In-Reply-To: <BL2FFO11FD05378650E02EA6549B4DF50E8030@BL2FFO11FD053.protection.gbl>
On Tue, Mar 17, 2015 at 09:48:15PM +0530, Nava kishore Manne wrote:
> In slave monitor mode, the I2C interface is set up as a master and
> continues to attempt a transfer to a particular slave until the
> slave device responds with an ACK.
>
> Added this feature for zero length transfers enable the controller
> for slave monitor interrupt and get the status. Disable the slave
> monitor mode feature upon successful handling.
>
> Signed-off-by: Nava kishore Manne <navam@xilinx.com>
> Acked-by: Harini Katakam <harinik@xilinx.com>
I am not sure this is going to work.
How often is this access tried when there is no device? It should be
tried only once.
Those 0byte messages can be read or write, so transferring one bit, one
could say. I assume this one can only read? (which is not a show-stopper
but the cases should be handled)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150327/d0a9ab91/attachment.sig>
next prev parent reply other threads:[~2015-03-27 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 16:18 [PATCH] i2c: cadence: Handling Slave monitor mode Nava kishore Manne
2015-03-27 15:37 ` Wolfram Sang [this message]
2015-04-02 20:09 ` Harini Katakam
2015-04-02 20:29 ` Wolfram Sang
2015-04-04 13:14 ` Nava kishore Manne
2015-04-04 15:34 ` 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=20150327153713.GC27238@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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).