From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pokefinder.org (sauhun.de [89.238.76.85]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3s2rdn3M28zDqQ9 for ; Mon, 1 Aug 2016 17:32:42 +1000 (AEST) Date: Mon, 1 Aug 2016 09:32:27 +0200 From: Wolfram Sang To: Christian Zigotzky Cc: Darren Stevens , Olof Johansson , linuxppc-dev@lists.ozlabs.org, luigi burdo , Julian Margetson , Steven Jeffery , "R.T.Dickinson" , "R.T.Dickinson" , Pat Wall , Pat Wall , "contact@a-eon.com" , "matthew@a-eon.biz" , Kevin Saunders , Lyle Hazelwood , EntwicklerX , "xray@relec.ch" , Steve-David Marguet , George Sokianos , Sinan =?utf-8?Q?G=C3=BCrkan?= , Mike , Thomas Ferreira , Christian Zigotzky , "pjs@pjsa.net" , Ben Cato Malkenes , linux-i2c@vger.kernel.org Subject: Re: [pasemi] problem with i2c-pasemi Message-ID: <20160801073227.GA1691@katana> References: <8b0682d3-866a-31dd-f01b-3510f84307dc@xenosoft.de> <2847029a-e3a4-8099-b72f-89d5731baaed@xenosoft.de> <6ebc8c6f-ffee-ab4e-1ce1-bc29bf08569d@xenosoft.de> <20160730182012.GA1608@katana> <20160731063656.GA1606@katana> <5f044abb-6ff3-6b65-68f3-e7348a8f6e8c@xenosoft.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" In-Reply-To: <5f044abb-6ff3-6b65-68f3-e7348a8f6e8c@xenosoft.de> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 31, 2016 at 09:36:00AM +0200, Christian Zigotzky wrote: > Here you are: >=20 > i2c-0 i2c Radeon i2c bit bus 0x90 I2C adapter > i2c-1 i2c Radeon i2c bit bus 0x91 I2C adapter > i2c-2 i2c Radeon i2c bit bus 0x92 I2C adapter > i2c-3 i2c Radeon i2c bit bus 0x93 I2C adapter > i2c-4 i2c Radeon i2c bit bus 0x94 I2C adapter > i2c-5 i2c Radeon i2c bit bus 0x95 I2C adapter > i2c-6 i2c Radeon i2c bit bus 0x96 I2C adapter > i2c-7 i2c Radeon i2c bit bus 0x97 I2C adapter > i2c-8 i2c card0-DP-1 I2C adapter > i2c-9 i2c card0-DP-2 I2C adapter Thanks. So, that means you don't have any bus from i2c-pasemi, since all numbered busses it wants to have [0-2] are already taken by the Radeon card. This has always been the case, no change in behaviour since 2008. Only since last merge window, the I2C core just reports this conflict. Maybe a bit too noisy? I don't think using i2c_add_numbered_adapter is a good idea together with PCI cards. I'd prefer to see i2c_add_adapter used. However, I don't know the platform at all and if there is someone relying on a static numbering scheme? I would assume this is not the case, because nobody really noticed that the busses do not probe for a while. Anyone here with more insight about PASEMI platform? --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJXnvsLAAoJEBQN5MwUoCm2IUEQAK+/yd+JUutn+HaZGfrdfT3L WaS+BGQS39kGyoSDMZKDQK8ttVcMY2VhBKaI0NqO4rk5+E870vtiS2qcwVNZnhrb Ile4YBndXn28rJqfRirfBu/e605X0EPopCtljemxYKfemYvmeOQ4E4WxcRwyfQLt fY2Y9hxoqKzeGOvAFKC8Fp1aylGC4pdqZVyHaElwjUYGKhdz+hymYGnhAqR4JCq1 +4Ow2ZMKbuoemwf4bsaaZShQLcX9/rvVxsrk9PgaenVVDPOq5yCtpwH5rj4kx5ne FyvKFKST6yfo6nb89T0ySQ5gr52pLZPMKlK8nBNH8/3Xerv5aPWD0edkStl680jD sjnrIvLvcsUZKLGoBJ7+XzScCq4Jg8UV5p/GWHgyCKJ5tMgo1tCF92ztQBtLrvEp VC7OIydezdAKLok3cxvAg78eBrg7Y3hZoNm+mFCwCxNvzGGSKmn8Q+KorNk7tEXh /Yiev+tNufYYD2UQFIBHsp+e8DaLyls1Fc3CUzbf+2z5B1ClOVXrXs8o5AJ+hYEg 8PffqvNEMZyHFqXacoBiSbVGVdRjpGBbCNqaAYDYijwTuXu1nFRFggix7UY6QLSi MQRhAZhmAM9FKGiMN5W3uVxf51S3iWP64Oju8+aY44EmonROzcClN9iFon/TKb5d jWIVrPO+cFqJbl2nJDVd =QKYX -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ--