| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 21 Jul 2009 17:23:36 +0200 From: Arnd Bergmann <arnd@...db.de> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: "Gurudatt, Sreenidhi B" <sreenidhi.b.gurudatt@...el.com>, "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Alan Cox <alan@...ux.intel.com> Subject: Re: x86: IPC driver patch for Intel Moorestown platform On Tuesday 21 July 2009, Alan Cox wrote: > > 1. built-in code adds platform-device for mrst_ipc > > 2. user space auto-loads the mrst_ipc driver > > 3. mrst_ipc driver creates child devices for each of its attached > > devices > > The devices talking to it already are devices - but they will be input > devices, watchdogs, etc. They already belong in existing classes. Remember that devices normally are both in the /sys/class hierarchy as a class device and in the /sys/devices hierarchy based on their attachment. > I also don't believe the mrst ipc is enumerable either. If it was > enumerable it would make a lot more sense. It could be done along the same lines as ./drivers/input/serio/i8042.c: The platform knows when an i8042 chip is present and adds the serio devices it statically knows about. The serio driver then adds input class devices for them. You probably wouldn't /have/ to add a new bus_type but could reuse nested platform devices. Arnd <>< -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists