Thomas Zimmermann <tzimmermann@xxxxxxx> writes: > Set the firmware framebuffer's parent device, which usually is the > graphics hardware's physical device. Integrates the framebuffer in > the Linux device hierarchy and lets Linux handle dependencies among > devices. For example, the graphics hardware won't be suspended while > the firmware device is still active. > > Signed-off-by: Thomas Zimmermann <tzimmermann@xxxxxxx> > --- > drivers/firmware/sysfb.c | 11 ++++++++++- > drivers/firmware/sysfb_simplefb.c | 5 ++++- > include/linux/sysfb.h | 3 ++- > 3 files changed, 16 insertions(+), 3 deletions(-) > > diff --git a/drivers/firmware/sysfb.c b/drivers/firmware/sysfb.c > index 19706bd2642a..8a42da3f67a9 100644 > --- a/drivers/firmware/sysfb.c > +++ b/drivers/firmware/sysfb.c > @@ -29,6 +29,7 @@ > #include <linux/init.h> > #include <linux/kernel.h> > #include <linux/mm.h> > +#include <linux/pci.h> > #include <linux/platform_data/simplefb.h> > #include <linux/platform_device.h> > #include <linux/screen_info.h> > @@ -72,6 +73,8 @@ EXPORT_SYMBOL_GPL(sysfb_disable); > static __init int sysfb_init(void) > { > const struct screen_info *si = &screen_info; > + struct device *parent = NULL; > + struct pci_dev *pparent; Maybe pci_parent? It's easier to read than pparent IMO. Reviewed-by: Javier Martinez Canillas <javierm@xxxxxxxxxx> -- Best regards, Javier Martinez Canillas Core Platforms Red Hat