From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751339AbdGaTR1 (ORCPT ); Mon, 31 Jul 2017 15:17:27 -0400 Received: from www.zeus03.de ([194.117.254.33]:36082 "EHLO mail.zeus03.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750999AbdGaTRY (ORCPT ); Mon, 31 Jul 2017 15:17:24 -0400 Date: Mon, 31 Jul 2017 21:17:21 +0200 From: Wolfram Sang To: Boris Brezillon Cc: linux-i2c@vger.kernel.org, Jonathan Corbet , linux-doc@vger.kernel.org, Greg Kroah-Hartman , Arnd Bergmann , Przemyslaw Sroka , Arkadiusz Golec , Alan Douglas , Bartosz Folta , Damian Kos , Alicja Jurasik-Urbaniak , Jan Kotas , Cyprian Wronka , Alexandre Belloni , Thomas Petazzoni , Nishanth Menon , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC 2/5] i3c: Add core I3C infrastructure Message-ID: <20170731191721.GA1542@katana> References: <1501518290-5723-1-git-send-email-boris.brezillon@free-electrons.com> <1501518290-5723-3-git-send-email-boris.brezillon@free-electrons.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: <1501518290-5723-3-git-send-email-boris.brezillon@free-electrons.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > +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. --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAll/gj0ACgkQFA3kzBSg KbZJzRAAldnFRC1tvImhgxmo3kHYW0c/2ICSWaj1rJd7sbypvsSY99wI5RtRwi1J odmdukQQvdbfKMhIDv+XmV/cIlffSL9iQR+8/EUbjR0gnvFEM7JMZdmR+70qiUaT h7hgfi+okPXmDr80ZBLTGsAje2cG5u7iiAFsvL1BOMrCc7ldNnY4o2L1f8rgL8OM 79dRV8MBGkBpyvs0H0ZiYtuOIoxYTL4X4zzl6RKlBmO9+n9pRMjjRD2oI2nlB7ZR dFnHP7HRxykQAWoh9PJ62guyf1i2BH4ea990v/+3U5ugowZRWvtkrE7AQSa1V0To F2AeApIBFaA1kszTZdqQc0Of8P0DYypPK+ko6qKYbpN1bX83ast1976NA27gOJ9i ZdblFygMG2GZ7eTYD6pjPBHC6uZCyVl7jfXP5tFivpOkZA7RqzfeZidD+3l/4m/B noC4XAznWSikUqpiRdJRUzX225/JV08K10EK4HRof58veQL4kgPCstFXoElp42PG wFQwTYvqJJtELpcMSnjJPLfuCcHq6HQvuoCHqtTktpg/xXDvPb9vNyYupU5EA/C4 Q8QllvzUL1cEOoGCNtzYdNPuk9KfGfzRO4cdiSy6hNDWGgmt0xUdyD7lrzAOHk9V pIk88FzLUixTuNYRqMkmRybw187dkCiEdl0aVQNQyiJESikqX0I= =Ll99 -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfram Sang Subject: Re: [RFC 2/5] i3c: Add core I3C infrastructure Date: Mon, 31 Jul 2017 21:17:21 +0200 Message-ID: <20170731191721.GA1542@katana> References: <1501518290-5723-1-git-send-email-boris.brezillon@free-electrons.com> <1501518290-5723-3-git-send-email-boris.brezillon@free-electrons.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Return-path: Content-Disposition: inline In-Reply-To: <1501518290-5723-3-git-send-email-boris.brezillon@free-electrons.com> Sender: linux-i2c-owner@vger.kernel.org To: Boris Brezillon Cc: linux-i2c@vger.kernel.org, Jonathan Corbet , linux-doc@vger.kernel.org, Greg Kroah-Hartman , Arnd Bergmann , Przemyslaw Sroka , Arkadiusz Golec , Alan Douglas , Bartosz Folta , Damian Kos , Alicja Jurasik-Urbaniak , Jan Kotas , Cyprian Wronka , Alexandre Belloni , Thomas Petazzoni , Nishanth Menon , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell List-Id: devicetree@vger.kernel.org --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > +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. --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAll/gj0ACgkQFA3kzBSg KbZJzRAAldnFRC1tvImhgxmo3kHYW0c/2ICSWaj1rJd7sbypvsSY99wI5RtRwi1J odmdukQQvdbfKMhIDv+XmV/cIlffSL9iQR+8/EUbjR0gnvFEM7JMZdmR+70qiUaT h7hgfi+okPXmDr80ZBLTGsAje2cG5u7iiAFsvL1BOMrCc7ldNnY4o2L1f8rgL8OM 79dRV8MBGkBpyvs0H0ZiYtuOIoxYTL4X4zzl6RKlBmO9+n9pRMjjRD2oI2nlB7ZR dFnHP7HRxykQAWoh9PJ62guyf1i2BH4ea990v/+3U5ugowZRWvtkrE7AQSa1V0To F2AeApIBFaA1kszTZdqQc0Of8P0DYypPK+ko6qKYbpN1bX83ast1976NA27gOJ9i ZdblFygMG2GZ7eTYD6pjPBHC6uZCyVl7jfXP5tFivpOkZA7RqzfeZidD+3l/4m/B noC4XAznWSikUqpiRdJRUzX225/JV08K10EK4HRof58veQL4kgPCstFXoElp42PG wFQwTYvqJJtELpcMSnjJPLfuCcHq6HQvuoCHqtTktpg/xXDvPb9vNyYupU5EA/C4 Q8QllvzUL1cEOoGCNtzYdNPuk9KfGfzRO4cdiSy6hNDWGgmt0xUdyD7lrzAOHk9V pIk88FzLUixTuNYRqMkmRybw187dkCiEdl0aVQNQyiJESikqX0I= =Ll99 -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V--