From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m4D8anM8004343 for ; Tue, 13 May 2008 04:36:49 -0400 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx3.redhat.com (8.13.8/8.13.8) with ESMTP id m4D8aIBQ019787 for ; Tue, 13 May 2008 04:36:18 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Jvpza-0001oo-0M for video4linux-list@redhat.com; Tue, 13 May 2008 08:36:14 +0000 Received: from 82-135-208-232.static.zebra.lt ([82.135.208.232]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 May 2008 08:36:13 +0000 Received: from augulis.darius by 82-135-208-232.static.zebra.lt with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 May 2008 08:36:13 +0000 To: video4linux-list@redhat.com From: Darius Date: Tue, 13 May 2008 11:31:15 +0300 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-13; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: Subject: Re: question about SoC Camera driver (Micron) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: video4linux-list-bounces@redhat.com Errors-To: video4linux-list-bounces@redhat.com List-ID: Guennadi Liakhovetski wrote: > On Mon, 12 May 2008, Darius wrote: > >> I have question regarding both camera drivers for mt9v022 and mt9m001. >> How does attach these drivers to i2c adapter? In i2c_driver structure there >> are neither .attach_adapter nor .detach_client members. So, how does these >> drivers comunicate via i2c bus? Have I something missed...? > > They are, so called, new style i2c drivers. They use .probe and .remove > members, see source code for details. > > Thanks > Guennadi > --- > Guennadi Liakhovetski Now I see how it works. I2C devices should be created before driver loading. There was my mistake, and driver does not call probe() function. Maybe would be better to create I2C devices by driver itself, not by the board specific config code? Now sensor driver is useless itself, without board specific configuration... Would be correct to do so? Thanks, Darius. -- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list