Re: [RFC] New system device API

Pavel Machek (pavel@suse.cz)
Mon, 9 Jun 2003 23:23:48 +0200


Hi!

> > Okay, but you should keep "new" functions as similar to existing ones
> > as possible. That means 3 parameters for suspend functions, and as
> > similar semantics to existing callbacks as possible.
>
> Did you read the earlier posts? They are similar, and simplified because
> they don't need the level, since all suspend/resume is expected to happen
> with interrupts disabled. The semantics are obvious, the deviation
> trivial, and this thread a dead horse.

The deviation is *not* trivial, and because I can not give you example
does not mean it does not exist.

> > > So? A keyboard controller is not classified as a system device.
> >
> > Its not on pci, I guess it would end up as a system device...
>
> Huh? Since when is everything that's not PCI a system device? Please read
> the documentation, esp. WRT system and platform devices.

Well, can you be a little more concrete? I do not see any description
about what is system device and what is not.

Keyboard controller is very deeply integrated into the system. If it
is not system device, what is it?
Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/