[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sat, 4 Apr 2015 17:34:47 +0200
From: Wolfram Sang <wsa@...-dreams.de>
To: Nava kishore Manne <nava.manne@...inx.com>
Cc: Harini Katakam <harinikatakamlinux@...il.com>,
Michal Simek <michals@...inx.com>,
Soren Brinkmann <sorenb@...inx.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Anirudha Sarangi <anirudh@...inx.com>,
Srikanth Vemula <svemula@...inx.com>
Subject: Re: [PATCH] i2c: cadence: Handling Slave monitor mode
> > So, it is kind of flooding the bus until the timeout? That is not a single zero
> > byte message.
> >
> It will not flooding the bus until the timeout. Once it fails to access the bus it will be ideal for 15 clock cycles. Master again retrying to access the
> Slave immediately after the 15 clock cycles (There is a register in the controller to set the retry value min: 0 cycles, max: 16 cycles).This process will repeat until
> The software timeout will happen (1000msec).
Compared to do one access only this is "kind of flooding", no?
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists