Re: shamcop adc

Selon Phil Blundell <pb_at_nexus.co.uk>:

> on Tue, Mar 02, 2004 at 05:33:59PM +0100, Alain2210 wrote:
> > Yes I can do that but then I get a message saying it cannot claim the
> resource.
> > And the
> > device adc shamcop cannot be defined without parent (I get a kernel oops).
>
> Inability to claim the resource shouldn't be fatal. So long as
> shamcop_base is giving it the right resource pointers, the driver should
> still work.

Yes but the soc-device make a release of the resource in that case. I have
canceled this but the adc shamcop device is then not initialised.
>
> > I have also reading the 2.4 kernel but I don't see exactly where the
> touchscreen was
> > managed.
>
> 2.4 had a completely different arrangement for these drivers; it didn't
> use soc-device at all. The touchscreen management actually happens in
> arch/arm/mach-pxa/h5400_asic_io.c, but I doubt this code will help you
> very much.

Thanks, I have began to give some look on it.

Alain
Received on Tue Mar 02 2004 - 16:59:07 EST