From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nommos.sslcatacombnetworking.com (nommos.sslcatacombnetworking.com [67.18.224.114]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 8EC78DDFCD for ; Thu, 25 Jan 2007 16:45:56 +1100 (EST) In-Reply-To: <20070125045617.40490.qmail@web53115.mail.yahoo.com> References: <20070125045617.40490.qmail@web53115.mail.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: From: Kumar Gala Subject: Re: [PATCH] I2C: Add I2C support for the MPC8260 Date: Wed, 24 Jan 2007 23:44:57 -0600 To: jimmy liu Cc: linuxppc-dev@ozlabs.org, hs@denx.de List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Jan 24, 2007, at 10:56 PM, jimmy liu wrote: > When I add mpc8260 I2C driver to Linux Kernel 2.6.19, > the init function looks like that > static int __init fsl_i2c_init(void) > { > return driver_register(&fsl_i2c_driver); > } > > I set the debug on, and found that the fsl_i2c_probe() > function is never > called, so there is not I2C device enabled, and the > user space function > open("/dev/i2c-0",O_RDWR) always return error. I set > something wrong? You need something to create a device to match the driver you've just registered. This has usually been done with the platform bus and using platform_devices in the past. - k