Re: [PATCH] PNP support for i8042 driver

Adam Belay
2004-11-16T06:26:49Z

On Tue, Nov 16, 2004 at 01:06:46AM -0500, Dmitry Torokhov wrote:
> Adam,
>
> I agree with your point that every device in the system should have a
> driver attached. And i8042 does have one bound to it. It is i8042 platform
> driver that does power management and ensures proper integration into driver
> model.
>
> There is no need to keep secondary "drivers" around, their sole purpose is
> to provide information about avalilable resources. It would be ok if the
> code was shared among several devices on a bus but for most (all?) legacy
> devices it has to be programmed explicitely and will not be reused.

Platform drivers are secondary drivers. They're crude hacks used to get a
minimal device into the driver model. They're necessary because ISA devices
cannot be detected like other types of devices. Why not use a system with
actual complete bus functionality like ACPI? If ACPI is available, then there
should be no need to create a platform device.

>
> Also i8042 should not rely on either ACPI or PNP simply because the driver/
> chip works on boxes other than x86/ia64 so we can't make ACPI or PNP drivers
> "main" ones.

No, but they should take priority when they are available. Don't forget that
there is also Open Firmware, which has similar functionalility to ACPI if I
understand correctly.

>
> As far as binding/rebinding goes I guess sysdevs and platform devices will
> just disable this functionality.

Exactly, they have limits because they are not real devices. ACPI devices are
real devices. They have resource management capabilities, power dependencies,
physical parents, and other features found in buses like PCI.

Thanks,
Adam