From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Stein Subject: i2c-eg20t: regression since i2c_add_numbered_adapter change Date: Wed, 22 Aug 2012 08:30:35 +0200 Message-ID: <4401854.hVfHzgeqjT@ws-stein> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Jean Delvare (PC drivers, core)" , "Ben Dooks (embedded platforms)" , Feng Tang , Tomoya MORINAGA List-Id: linux-i2c@vger.kernel.org Hello, I just noticed the 3.4 linux kernel fails to sucessfully probe the i2c-eg20t driver. I returns with EBUSY error. It worked on the 3.0 kernel. To my view it is caused the commit 07e8a51ff68353e01d795cceafbac9f54c49132b ( i2c-eg20t: use i2c_add_numbered_adapter to get a fixed bus number). The reason it actually fails is that the i2c-isch driver is registered beforehand which gets bus number 0. But this one is the bus number the eg20t driver wants to register. A possibility is that if i2c_add_numbered_adapter failed with EBUSY just use i2c_add_adapter to get at least the driver working, but with a non-fixed bus number. Opinions? Best regards, Alexander