Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751569Ab3FYORM (ORCPT ); Tue, 25 Jun 2013 10:17:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:63406 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751113Ab3FYORK (ORCPT ); Tue, 25 Jun 2013 10:17:10 -0400 Date: Tue, 25 Jun 2013 10:17:04 -0400 From: Josh Boyer To: Peter Jones Cc: Florian Tobias Schandinat , linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Handle efifb with no lfb_base better. Message-ID: <20130625141703.GB9410@hansolo.jdub.homelinux.org> References: <1366730598-13942-1-git-send-email-pjones@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1366730598-13942-1-git-send-email-pjones@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2921 Lines: 85 On Tue, Apr 23, 2013 at 11:23:18AM -0400, Peter Jones wrote: > Right now we get a WARN from platform_device_unregister() because our > platform_device has no ->release function. This is clearly wrong, but > we should be warning so we can figure out what happened, as this failure > results in bug reports. So WARN() about the real problem, and use the > registration function that gives us a default release() function. > > This fixes the tracback reported at > https://bugzilla.redhat.com/show_bug.cgi?id=840621 , though it does not > fix the actual /problem/ the user is seeing. > > Signed-off-by: Peter Jones Is anyone in the fdbdev camp looking at this? It's been 2 months since this was sent out without any comments and I don't see it in the tree anywhere. josh > --- > drivers/video/efifb.c | 15 ++++++++------- > 1 file changed, 8 insertions(+), 7 deletions(-) > > diff --git a/drivers/video/efifb.c b/drivers/video/efifb.c > index 50fe668..390b61b 100644 > --- a/drivers/video/efifb.c > +++ b/drivers/video/efifb.c > @@ -285,6 +285,7 @@ static void efifb_destroy(struct fb_info *info) > { > if (info->screen_base) > iounmap(info->screen_base); > + fb_dealloc_cmap(&info->cmap); > if (request_mem_succeeded) > release_mem_region(info->apertures->ranges[0].base, > info->apertures->ranges[0].size); > @@ -382,6 +383,8 @@ static int __init efifb_probe(struct platform_device *dev) > if (!screen_info.pages) > screen_info.pages = 1; > if (!screen_info.lfb_base) { > + WARN(1, KERN_WARNING, "invalid framebuffer address for " > + "device '%s'\n", dev_name(dev)); > printk(KERN_DEBUG "efifb: invalid framebuffer address\n"); > return -ENODEV; > } > @@ -544,9 +547,7 @@ static struct platform_driver efifb_driver = { > }, > }; > > -static struct platform_device efifb_device = { > - .name = "efifb", > -}; > +static struct platform_device *efifb_device; > > static int __init efifb_init(void) > { > @@ -571,9 +572,9 @@ static int __init efifb_init(void) > if (!screen_info.lfb_linelength) > return -ENODEV; > > - ret = platform_device_register(&efifb_device); > - if (ret) > - return ret; > + efifb_device = platform_device_register_simple("efifb", 0, NULL, 0); > + if (IS_ERROR(efifb_device)) > + return PTR_ERR(efifb_device); > > /* > * This is not just an optimization. We will interfere > @@ -582,7 +583,7 @@ static int __init efifb_init(void) > */ > ret = platform_driver_probe(&efifb_driver, efifb_probe); > if (ret) { > - platform_device_unregister(&efifb_device); > + platform_device_unregister(efifb_device); > return ret; > } > > -- > 1.8.1.4 > -- 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/