From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 40ED4C4338F for ; Fri, 13 Aug 2021 13:46:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 183C060F11 for ; Fri, 13 Aug 2021 13:46:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240042AbhHMNrO (ORCPT ); Fri, 13 Aug 2021 09:47:14 -0400 Received: from mga12.intel.com ([192.55.52.136]:5895 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240648AbhHMNrN (ORCPT ); Fri, 13 Aug 2021 09:47:13 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10074"; a="195146313" X-IronPort-AV: E=Sophos;i="5.84,319,1620716400"; d="scan'208";a="195146313" Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Aug 2021 06:46:46 -0700 X-IronPort-AV: E=Sophos;i="5.84,319,1620716400"; d="scan'208";a="508268612" Received: from ideak-desk.fi.intel.com ([10.237.68.141]) by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Aug 2021 06:46:44 -0700 Date: Fri, 13 Aug 2021 16:46:41 +0300 From: Imre Deak To: linux-fbdev@vger.kernel.org, Daniel Vetter , Kai-Heng Feng , Alex Deucher Cc: dri-devel@lists.freedesktop.org, Thomas Zimmermann , intel-gfx@lists.freedesktop.org Subject: Re: [Intel-gfx] [PATCH v2] fbdev/efifb: Release PCI device's runtime PM ref during FB destroy Message-ID: <20210813134641.GA2652433@ideak-desk.fi.intel.com> References: <20210802133551.1904964-1-imre.deak@intel.com> <20210809133146.2478382-1-imre.deak@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210809133146.2478382-1-imre.deak@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-fbdev@vger.kernel.org On Mon, Aug 09, 2021 at 04:31:46PM +0300, Imre Deak wrote: > Atm the EFI FB platform driver gets a runtime PM reference for the > associated GFX PCI device during probing the EFI FB platform device and > releases it only when the platform device gets unbound. > > When fbcon switches to the FB provided by the PCI device's driver (for > instance i915/drmfb), the EFI FB will get only unregistered without the > EFI FB platform device getting unbound, keeping the runtime PM reference > acquired during the platform device probing. This reference will prevent > the PCI driver from runtime suspending the device. > > Fix this by releasing the RPM reference from the EFI FB's destroy hook, > called when the FB gets unregistered. > > While at it assert that pm_runtime_get_sync() didn't fail. > > v2: > - Move pm_runtime_get_sync() before register_framebuffer() to avoid its > race wrt. efifb_destroy()->pm_runtime_put(). (Daniel) > - Assert that pm_runtime_get_sync() didn't fail. > - Clarify commit message wrt. platform/PCI device/driver and driver > removal vs. device unbinding. > > Fixes: a6c0fd3d5a8b ("efifb: Ensure graphics device for efifb stays at PCI D0") > Cc: Kai-Heng Feng > Cc: Daniel Vetter > Reviewed-by: Daniel Vetter (v1) > Signed-off-by: Imre Deak Thanks for the reviews, pushed to drm-intel-next. > --- > drivers/video/fbdev/efifb.c | 21 ++++++++++++++------- > 1 file changed, 14 insertions(+), 7 deletions(-) > > diff --git a/drivers/video/fbdev/efifb.c b/drivers/video/fbdev/efifb.c > index 8ea8f079cde26..edca3703b9640 100644 > --- a/drivers/video/fbdev/efifb.c > +++ b/drivers/video/fbdev/efifb.c > @@ -47,6 +47,8 @@ static bool use_bgrt = true; > static bool request_mem_succeeded = false; > static u64 mem_flags = EFI_MEMORY_WC | EFI_MEMORY_UC; > > +static struct pci_dev *efifb_pci_dev; /* dev with BAR covering the efifb */ > + > static struct fb_var_screeninfo efifb_defined = { > .activate = FB_ACTIVATE_NOW, > .height = -1, > @@ -243,6 +245,9 @@ static inline void efifb_show_boot_graphics(struct fb_info *info) {} > > static void efifb_destroy(struct fb_info *info) > { > + if (efifb_pci_dev) > + pm_runtime_put(&efifb_pci_dev->dev); > + > if (info->screen_base) { > if (mem_flags & (EFI_MEMORY_UC | EFI_MEMORY_WC)) > iounmap(info->screen_base); > @@ -333,7 +338,6 @@ ATTRIBUTE_GROUPS(efifb); > > static bool pci_dev_disabled; /* FB base matches BAR of a disabled device */ > > -static struct pci_dev *efifb_pci_dev; /* dev with BAR covering the efifb */ > static struct resource *bar_resource; > static u64 bar_offset; > > @@ -569,17 +573,22 @@ static int efifb_probe(struct platform_device *dev) > pr_err("efifb: cannot allocate colormap\n"); > goto err_groups; > } > + > + if (efifb_pci_dev) > + WARN_ON(pm_runtime_get_sync(&efifb_pci_dev->dev) < 0); > + > err = register_framebuffer(info); > if (err < 0) { > pr_err("efifb: cannot register framebuffer\n"); > - goto err_fb_dealoc; > + goto err_put_rpm_ref; > } > fb_info(info, "%s frame buffer device\n", info->fix.id); > - if (efifb_pci_dev) > - pm_runtime_get_sync(&efifb_pci_dev->dev); > return 0; > > -err_fb_dealoc: > +err_put_rpm_ref: > + if (efifb_pci_dev) > + pm_runtime_put(&efifb_pci_dev->dev); > + > fb_dealloc_cmap(&info->cmap); > err_groups: > sysfs_remove_groups(&dev->dev.kobj, efifb_groups); > @@ -603,8 +612,6 @@ static int efifb_remove(struct platform_device *pdev) > unregister_framebuffer(info); > sysfs_remove_groups(&pdev->dev.kobj, efifb_groups); > framebuffer_release(info); > - if (efifb_pci_dev) > - pm_runtime_put(&efifb_pci_dev->dev); > > return 0; > } > -- > 2.27.0 >