From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751992AbdHAR1I (ORCPT ); Tue, 1 Aug 2017 13:27:08 -0400 Received: from www.zeus03.de ([194.117.254.33]:51080 "EHLO mail.zeus03.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751860AbdHAR1H (ORCPT ); Tue, 1 Aug 2017 13:27:07 -0400 Date: Tue, 1 Aug 2017 19:27:03 +0200 From: Wolfram Sang To: "Andrew F. Davis" Cc: Boris Brezillon , Arnd Bergmann , linux-i2c@vger.kernel.org, Jonathan Corbet , linux-doc@vger.kernel.org, Greg Kroah-Hartman , 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 Mailing List Subject: Re: [RFC 2/5] i3c: Add core I3C infrastructure Message-ID: <20170801172703.GA2737@katana> References: <1501518290-5723-1-git-send-email-boris.brezillon@free-electrons.com> <1501518290-5723-3-git-send-email-boris.brezillon@free-electrons.com> <20170731231509.77d1fba4@bbrezillon> <20170731214211.GA11776@tetsubishi> <1538596b-80ed-7800-db97-70e73b90b9e2@ti.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline In-Reply-To: <1538596b-80ed-7800-db97-70e73b90b9e2@ti.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 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > I'm surprised they didn't allow for slave clock stretching when > communicating with a legacy i2c device, it will prohibit use of a rather > large class of devices. :( Yes, but I3C is push/pull IIRC. > As for interrupts you are always free to wire up an out-of-band > interrupt like before. :) Yes, my wording was a bit too strong. It is possible, sure. Yet, I understood that one of the features of I3C is to have in-band interrupt support. We will see if the demand for backward compatibility or "saving pins" is higher. --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAlmAueMACgkQFA3kzBSg KbbOow//VRF0acsc9HmV4bEcTZJwiiHER6G15l+GI4eaHcHxxK3xnjBZykh73SHh I1TvBVUTJQyiVbsc/jypBfhfPgIeMgcLDMfKKQJfR67im6/6yIY84qtxBCKemGhf l3q5p1nEjnKjK9KpQ1nLoKBgQy27L1lO1gMIECGoGBz+9piSm1hGjg7tO3ecmq+Q OV7UVbb9iJX/4gMZ0ot4pCj0sha3puemoC77Wtix5RCWDhjgSaV+0De0jJNdDV2L XKIZlAoICFIReVRSlyzlamXH3WsCSHbV4pWS/gwhmWAChhuQn2vW1HIsfq5QztTf QphJYqdLoy9qLaRzrJls0wPWRA0FirfKfyJhWdQuZ3kn+pU1el49dj6GM1v32PSk howTjyGpufWnvfgOwGrkndMTx4fiamH9yFfG4ci3OPG4akpup7uEzGvWPCzOypUz KoJNiIDbmWOGWfxr8p3ExAt8wQIDfFmp4mRnFi4ruKSh9Ry+dR4v9Ho56PV/vBLm ZRWxAPAPBmEtJfxSaWL1Bd2LuynwvGcv8bTqDHgFFBC7xaOz/fAxYxsUk/DThZG4 3c+e8aFMu1aX+nIb2kaUv0clXd7ULg3k8ZRsmQiD+Xj700IG6W1gd///39jIGdZ5 rJVLzLczJq3l55/cyRnn0+ug+aAFmzOKax6c7t6q/7WKGV2fP6k= =1e44 -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfram Sang Subject: Re: [RFC 2/5] i3c: Add core I3C infrastructure Date: Tue, 1 Aug 2017 19:27:03 +0200 Message-ID: <20170801172703.GA2737@katana> References: <1501518290-5723-1-git-send-email-boris.brezillon@free-electrons.com> <1501518290-5723-3-git-send-email-boris.brezillon@free-electrons.com> <20170731231509.77d1fba4@bbrezillon> <20170731214211.GA11776@tetsubishi> <1538596b-80ed-7800-db97-70e73b90b9e2@ti.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Return-path: Content-Disposition: inline In-Reply-To: <1538596b-80ed-7800-db97-70e73b90b9e2@ti.com> Sender: linux-doc-owner@vger.kernel.org To: "Andrew F. Davis" Cc: Boris Brezillon , Arnd Bergmann , linux-i2c@vger.kernel.org, Jonathan Corbet , linux-doc@vger.kernel.org, Greg Kroah-Hartman , 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 List-Id: devicetree@vger.kernel.org --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > I'm surprised they didn't allow for slave clock stretching when > communicating with a legacy i2c device, it will prohibit use of a rather > large class of devices. :( Yes, but I3C is push/pull IIRC. > As for interrupts you are always free to wire up an out-of-band > interrupt like before. :) Yes, my wording was a bit too strong. It is possible, sure. Yet, I understood that one of the features of I3C is to have in-band interrupt support. We will see if the demand for backward compatibility or "saving pins" is higher. --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAlmAueMACgkQFA3kzBSg KbbOow//VRF0acsc9HmV4bEcTZJwiiHER6G15l+GI4eaHcHxxK3xnjBZykh73SHh I1TvBVUTJQyiVbsc/jypBfhfPgIeMgcLDMfKKQJfR67im6/6yIY84qtxBCKemGhf l3q5p1nEjnKjK9KpQ1nLoKBgQy27L1lO1gMIECGoGBz+9piSm1hGjg7tO3ecmq+Q OV7UVbb9iJX/4gMZ0ot4pCj0sha3puemoC77Wtix5RCWDhjgSaV+0De0jJNdDV2L XKIZlAoICFIReVRSlyzlamXH3WsCSHbV4pWS/gwhmWAChhuQn2vW1HIsfq5QztTf QphJYqdLoy9qLaRzrJls0wPWRA0FirfKfyJhWdQuZ3kn+pU1el49dj6GM1v32PSk howTjyGpufWnvfgOwGrkndMTx4fiamH9yFfG4ci3OPG4akpup7uEzGvWPCzOypUz KoJNiIDbmWOGWfxr8p3ExAt8wQIDfFmp4mRnFi4ruKSh9Ry+dR4v9Ho56PV/vBLm ZRWxAPAPBmEtJfxSaWL1Bd2LuynwvGcv8bTqDHgFFBC7xaOz/fAxYxsUk/DThZG4 3c+e8aFMu1aX+nIb2kaUv0clXd7ULg3k8ZRsmQiD+Xj700IG6W1gd///39jIGdZ5 rJVLzLczJq3l55/cyRnn0+ug+aAFmzOKax6c7t6q/7WKGV2fP6k= =1e44 -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8--