From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Thu, 30 Jun 2005 17:40:20 +0000 Subject: Re: sysdev_class use from DRM Message-Id: <20050630174020.GA11676@kroah.com> List-Id: References: <9e473391050624071263dfbea7@mail.gmail.com> In-Reply-To: <9e473391050624071263dfbea7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Jun 24, 2005 at 10:12:19AM -0400, Jon Smirl wrote: > DRM has a model where it runs without attaching to the PCI device. It > is doing this because the framebuffer devices are already attached to > the device. > > Some developers want to add power manager support to the DRM drivers. > Since the normal pm hooks are occupied they are doing this by creating > a sysdev_class. > > static struct sysdev_class drm_sysdev_class = { > set_kset_name("drm"), > .resume = drm_resume, > .suspend = drm_suspend, > }; Ick, don't do this, this is a hack. If you really just want to catch the reboot, add a reboot notifier hook to your driver. > Don't tell me to merge DRM/fbdev, that fight has been going on for two > years now. Well, that's the only real way to fix this. A simple single driver that handles the pci registering and doles out the resources and callbacks to the differnt DRM or fbdev driver is the way to go. I thought you all were working on this a year ago... thanks, greg k-h ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel