From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Nava kishore Manne <nava.manne-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Cc: Harini Katakam
<harinikatakamlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Michal Simek <michals-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
Soren Brinkmann <sorenb-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Anirudha Sarangi
<anirudh-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
Srikanth Vemula <svemula-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] i2c: cadence: Handling Slave monitor mode
Date: Sat, 4 Apr 2015 17:34:47 +0200 [thread overview]
Message-ID: <20150404153447.GA3808@katana> (raw)
In-Reply-To: <9ef3c612-b803-4937-bb21-0fac03969f39-reflc3kr++PT8KeBtZ6NpOhlVc3/7hDbVaz/vdPVXQ4@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
> > 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?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i2c: cadence: Handling Slave monitor mode
Date: Sat, 4 Apr 2015 17:34:47 +0200 [thread overview]
Message-ID: <20150404153447.GA3808@katana> (raw)
In-Reply-To: <9ef3c612-b803-4937-bb21-0fac03969f39@BN1AFFO11FD037.protection.gbl>
> > 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?
-------------- 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/20150404/b0929c3c/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: Harini Katakam <harinikatakamlinux@gmail.com>,
Michal Simek <michals@xilinx.com>,
Soren Brinkmann <sorenb@xilinx.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Anirudha Sarangi <anirudh@xilinx.com>,
Srikanth Vemula <svemula@xilinx.com>
Subject: Re: [PATCH] i2c: cadence: Handling Slave monitor mode
Date: Sat, 4 Apr 2015 17:34:47 +0200 [thread overview]
Message-ID: <20150404153447.GA3808@katana> (raw)
In-Reply-To: <9ef3c612-b803-4937-bb21-0fac03969f39@BN1AFFO11FD037.protection.gbl>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
> > 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?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-04 15:34 UTC|newest]
Thread overview: 18+ 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-17 16:18 ` Nava kishore Manne
2015-03-17 16:18 ` Nava kishore Manne
[not found] ` <BL2FFO11FD05378650E02EA6549B4DF50E8030-xjCwUguQ55+9TOEzIYUSF2YJ4DzVTqeXkX/xN29GLwg@public.gmane.org>
2015-03-27 15:37 ` Wolfram Sang
2015-03-27 15:37 ` Wolfram Sang
2015-03-27 15:37 ` Wolfram Sang
2015-04-02 20:09 ` Harini Katakam
2015-04-02 20:09 ` Harini Katakam
2015-04-02 20:09 ` Harini Katakam
[not found] ` <CAFcVECKaLBvOVvTca87-oTue5nF_pek_0msFZDD8y4yuCHW2EA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-02 20:29 ` Wolfram Sang
2015-04-02 20:29 ` Wolfram Sang
2015-04-02 20:29 ` Wolfram Sang
2015-04-04 13:14 ` Nava kishore Manne
2015-04-04 13:14 ` Nava kishore Manne
2015-04-04 13:14 ` Nava kishore Manne
[not found] ` <9ef3c612-b803-4937-bb21-0fac03969f39-reflc3kr++PT8KeBtZ6NpOhlVc3/7hDbVaz/vdPVXQ4@public.gmane.org>
2015-04-04 15:34 ` Wolfram Sang [this message]
2015-04-04 15:34 ` Wolfram Sang
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=20150404153447.GA3808@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=anirudh-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=harinikatakamlinux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michals-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=nava.manne-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=sorenb-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=svemula-gjFFaj9aHVfQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.