From: Wolfram Sang <wsa@the-dreams.de> To: Boris Brezillon <boris.brezillon@free-electrons.com> Cc: linux-i2c@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Arnd Bergmann <arnd@arndb.de>, Przemyslaw Sroka <psroka@cadence.com>, Arkadiusz Golec <agolec@cadence.com>, Alan Douglas <adouglas@cadence.com>, Bartosz Folta <bfolta@cadence.com>, Damian Kos <dkos@cadence.com>, Alicja Jurasik-Urbaniak <alicja@cadence.com>, Jan Kotas <jank@cadence.com>, Cyprian Wronka <cwronka@cadence.com>, Alexandre Belloni <alexandre.belloni@free-electrons.com>, Thomas Petazzoni <thomas.petazzoni@free-electrons.com>, Nishanth Menon <nm@ti.com>, Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>, Mark Rutland <mark.rutland@arm.com>, Ian Campbell <ijc+devicetree@hellion.org.uk>, Kumar Gala <galak@codeaurora.org>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC 2/5] i3c: Add core I3C infrastructure Date: Mon, 31 Jul 2017 21:17:21 +0200 [thread overview] Message-ID: <20170731191721.GA1542@katana> (raw) In-Reply-To: <1501518290-5723-3-git-send-email-boris.brezillon@free-electrons.com> [-- Attachment #1: Type: text/plain, Size: 945 bytes --] > +This document is just a brief introduction to the I3C protocol and the concepts > +it brings on the table. If you need more information, please refer to the MIPI > +I3C specification. I wish I could. > + > +Introduction > +============ > + > +The I3C (I-Cube-C) is a MIPI standardized protocol designed to overcome I2C "Eye-three-See", according to: http://eecatalog.com/sensors/2017/07/05/after-35-years-of-i2c-i3c-improves-capability-and-performance/ > +Backward compatibility with I2C devices > +======================================= > + > +The I3C protocol has been designed to be backward compatible with I2C devices. > +This backward compatibility allows one to connect a mix of I2C and I3C devices > +on the same bus, though, in order to be really efficient, I2C devices should > +be equipped with 50 ns spike filters. I just found a slide which says I3C does not support clock stretching. That should be mentioned here, too. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de> To: Boris Brezillon <boris.brezillon@free-electrons.com> Cc: linux-i2c@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Arnd Bergmann <arnd@arndb.de>, Przemyslaw Sroka <psroka@cadence.com>, Arkadiusz Golec <agolec@cadence.com>, Alan Douglas <adouglas@cadence.com>, Bartosz Folta <bfolta@cadence.com>, Damian Kos <dkos@cadence.com>, Alicja Jurasik-Urbaniak <alicja@cadence.com>, Jan Kotas <jank@cadence.com>, Cyprian Wronka <cwronka@cadence.com>, Alexandre Belloni <alexandre.belloni@free-electrons.com>, Thomas Petazzoni <thomas.petazzoni@free-electrons.com>, Nishanth Menon <nm@ti.com>, Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>, Mark Rutland <mark.rutland@arm.com>, Ian Campbell <ijc+devicetree@hellion.org.uk> Subject: Re: [RFC 2/5] i3c: Add core I3C infrastructure Date: Mon, 31 Jul 2017 21:17:21 +0200 [thread overview] Message-ID: <20170731191721.GA1542@katana> (raw) In-Reply-To: <1501518290-5723-3-git-send-email-boris.brezillon@free-electrons.com> [-- Attachment #1: Type: text/plain, Size: 945 bytes --] > +This document is just a brief introduction to the I3C protocol and the concepts > +it brings on the table. If you need more information, please refer to the MIPI > +I3C specification. I wish I could. > + > +Introduction > +============ > + > +The I3C (I-Cube-C) is a MIPI standardized protocol designed to overcome I2C "Eye-three-See", according to: http://eecatalog.com/sensors/2017/07/05/after-35-years-of-i2c-i3c-improves-capability-and-performance/ > +Backward compatibility with I2C devices > +======================================= > + > +The I3C protocol has been designed to be backward compatible with I2C devices. > +This backward compatibility allows one to connect a mix of I2C and I3C devices > +on the same bus, though, in order to be really efficient, I2C devices should > +be equipped with 50 ns spike filters. I just found a slide which says I3C does not support clock stretching. That should be mentioned here, too. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-31 19:17 UTC|newest] Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-07-31 16:24 [RFC 0/5] Add I3C subsystem Boris Brezillon 2017-07-31 16:24 ` [RFC 1/5] i2c: Export of_i2c_get_board_info() Boris Brezillon 2017-07-31 16:24 ` [RFC 2/5] i3c: Add core I3C infrastructure Boris Brezillon 2017-07-31 19:17 ` Wolfram Sang [this message] 2017-07-31 19:17 ` Wolfram Sang 2017-07-31 20:46 ` Boris Brezillon 2017-07-31 20:46 ` Boris Brezillon 2017-07-31 20:16 ` Arnd Bergmann 2017-07-31 20:16 ` Arnd Bergmann 2017-07-31 21:15 ` Boris Brezillon 2017-07-31 21:15 ` Boris Brezillon 2017-07-31 21:32 ` Peter Rosin 2017-07-31 21:32 ` Peter Rosin 2017-07-31 21:42 ` Wolfram Sang 2017-07-31 21:42 ` Wolfram Sang 2017-08-01 16:47 ` Andrew F. Davis 2017-08-01 16:47 ` Andrew F. Davis 2017-08-01 17:27 ` Wolfram Sang 2017-08-01 17:27 ` Wolfram Sang 2017-08-01 21:47 ` Boris Brezillon 2017-08-01 21:47 ` Boris Brezillon 2017-08-02 10:21 ` Wolfram Sang 2017-08-02 10:21 ` Wolfram Sang 2017-08-01 12:00 ` Arnd Bergmann 2017-08-01 12:00 ` Arnd Bergmann 2017-08-01 12:29 ` Boris Brezillon 2017-08-01 12:29 ` Boris Brezillon 2017-08-01 13:11 ` Arnd Bergmann 2017-08-01 13:11 ` Arnd Bergmann 2017-08-01 13:34 ` Boris Brezillon 2017-08-01 13:34 ` Boris Brezillon 2017-08-01 13:58 ` Boris Brezillon 2017-08-01 13:58 ` Boris Brezillon 2017-08-01 14:22 ` Arnd Bergmann 2017-08-01 14:22 ` Arnd Bergmann 2017-08-01 15:14 ` Boris Brezillon 2017-08-01 15:14 ` Boris Brezillon 2017-08-01 20:16 ` Arnd Bergmann 2017-08-01 20:16 ` Arnd Bergmann 2017-08-01 14:12 ` Wolfram Sang 2017-08-01 14:12 ` Wolfram Sang 2017-08-01 14:48 ` Boris Brezillon 2017-08-01 14:48 ` Boris Brezillon 2017-08-01 15:01 ` Wolfram Sang 2017-08-01 15:01 ` Wolfram Sang 2017-08-01 15:20 ` Boris Brezillon 2017-08-01 15:20 ` Boris Brezillon 2017-08-03 8:03 ` Boris Brezillon 2017-08-03 8:03 ` Boris Brezillon 2017-08-16 21:03 ` Geert Uytterhoeven 2017-08-16 21:03 ` Geert Uytterhoeven 2017-08-17 7:48 ` Boris Brezillon 2017-08-17 7:48 ` Boris Brezillon 2017-08-01 1:40 ` Greg Kroah-Hartman 2017-08-01 1:40 ` Greg Kroah-Hartman 2017-08-01 10:48 ` Boris Brezillon 2017-08-01 10:48 ` Boris Brezillon 2017-08-01 17:51 ` Greg Kroah-Hartman 2017-08-01 17:51 ` Greg Kroah-Hartman 2017-08-01 21:30 ` Boris Brezillon 2017-08-01 21:30 ` Boris Brezillon 2017-08-02 0:54 ` Greg Kroah-Hartman 2017-08-02 0:54 ` Greg Kroah-Hartman 2017-08-02 2:13 ` Greg Kroah-Hartman 2017-08-02 2:13 ` Greg Kroah-Hartman 2017-12-13 16:20 ` Boris Brezillon 2017-12-13 16:20 ` Boris Brezillon 2017-12-13 16:51 ` Greg Kroah-Hartman 2017-12-13 16:51 ` Greg Kroah-Hartman 2017-08-17 9:03 ` Linus Walleij 2017-08-17 9:03 ` Linus Walleij 2017-08-17 9:28 ` Boris Brezillon 2017-08-17 9:28 ` Boris Brezillon 2017-07-31 16:24 ` [RFC 3/5] dt-bindings: i3c: Document core bindings Boris Brezillon 2017-07-31 16:24 ` Boris Brezillon 2017-08-09 23:43 ` Rob Herring 2017-08-09 23:43 ` Rob Herring 2017-08-10 8:49 ` Boris Brezillon 2017-08-10 8:49 ` Boris Brezillon 2017-07-31 16:24 ` [RFC 4/5] i3c: master: Add driver for Cadence IP Boris Brezillon 2017-07-31 16:24 ` [RFC 5/5] dt-bindings: i3c: Document Cadence I3C master bindings Boris Brezillon 2017-07-31 19:17 ` [RFC 0/5] Add I3C subsystem Wolfram Sang 2017-07-31 19:17 ` Wolfram Sang 2017-07-31 20:40 ` Boris Brezillon 2017-07-31 20:40 ` Boris Brezillon 2017-07-31 20:47 ` Wolfram Sang 2017-07-31 20:47 ` Wolfram Sang 2017-12-12 19:58 ` Boris Brezillon 2017-12-12 19:58 ` Boris Brezillon 2017-12-12 22:01 ` Wolfram Sang 2017-12-12 22:01 ` 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=20170731191721.GA1542@katana \ --to=wsa@the-dreams.de \ --cc=adouglas@cadence.com \ --cc=agolec@cadence.com \ --cc=alexandre.belloni@free-electrons.com \ --cc=alicja@cadence.com \ --cc=arnd@arndb.de \ --cc=bfolta@cadence.com \ --cc=boris.brezillon@free-electrons.com \ --cc=corbet@lwn.net \ --cc=cwronka@cadence.com \ --cc=devicetree@vger.kernel.org \ --cc=dkos@cadence.com \ --cc=galak@codeaurora.org \ --cc=gregkh@linuxfoundation.org \ --cc=ijc+devicetree@hellion.org.uk \ --cc=jank@cadence.com \ --cc=linux-doc@vger.kernel.org \ --cc=linux-i2c@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=nm@ti.com \ --cc=pawel.moll@arm.com \ --cc=psroka@cadence.com \ --cc=robh+dt@kernel.org \ --cc=thomas.petazzoni@free-electrons.com \ /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: linkBe 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.