Hello,
Selon Phil Blundell <pb_at_nexus.co.uk>:
> on Wed, Mar 03, 2004 at 03:24:58PM +0100, Alain2210 wrote:
> > I'm trying to understand that. So, could you help me : when
> > shamcop_adc_probe (struct device *dev)
> > is called where is defined the value of dev ? I have not understood a basic
> thing.
>
> That probe function is called by the soc-device code in response to the
> soc_device_register(sdev) in shamcop_probe. The dev argument that
> shamcop_adc_probe() sees will be &sdev->device from shamcop_probe().
Yesterday, I have made some test about device.
It seems that the drivers are loaded with driver_register and the device is
found by
driver_attach.
The driver of the ipaq for which a device is searched are
ipaq shamcop
shamcop adc
shamcop ts
mq11xx_lcd
pxa2xx_serial
mq11xx_fb
mq11xx
ide-disk
ide-cs
pxa2xx-pcmcia
and the devices are
ipaq shamcop
mq11xx
pxamci
pxa-fb
pxa2xx_udc
pxa2xx_serial
pxa2xx-pcmcia
hence a matching is done and the drivers/devices are installed for
ipaq shamcop
pxa2xx_serial
mq11xx
pxa2xx-pcmcia
So do you know where is the problem for the ads/ts ? Is there a lack of a device ?
Thanks,
Alain
Received on Thu Mar 04 2004 - 13:42:33 EST
This archive was generated by hypermail 2.2.0 : Mon Jul 25 2005 - 17:19:25 EDT