From: Jani Nikula <jani.nikula@linux.intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: , Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix wrong name announced on FB driver switching
Date: Mon, 03 May 2021 20:38:17 +0300 [thread overview]
Message-ID: <87zgxbzpiu.fsf@intel.com> (raw)
In-Reply-To: <20210429134450.302912-1-janusz.krzysztofik@linux.intel.com>
On Thu, 29 Apr 2021, Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> wrote:
> Commit 7a0f9ef9703d ("drm/i915: Use drm_fb_helper_fill_info")
> effectively changed our FB driver name from "inteldrmfb" to
> "i915drmfb". However, we are still using the old name when kicking out
> a firmware fbdev driver potentially bound to our device. Use the new
> name to avoid confusion.
>
> Note: since the new name is assigned by a DRM fbdev helper called at
> the DRM driver registration time, that name is not available when we
> kick the other driver out early, hence a hardcoded name must be used
> unless the DRM layer exposes a macro for converting a DRM driver name
> to its associated fbdev driver name.
>
> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
LGTM, Daniel?
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
$ dim fixes 7a0f9ef9703d
Fixes: 7a0f9ef9703d ("drm/i915: Use drm_fb_helper_fill_info")
Cc: Noralf Trønnes <noralf@tronnes.org>
Cc: Alex Deucher <alexander.deucher@amd.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Cc: <stable@vger.kernel.org> # v5.2+
> ---
> drivers/gpu/drm/i915/i915_drv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index 785dcf20c77b..46082490dc9a 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -554,7 +554,7 @@ static int i915_driver_hw_probe(struct drm_i915_private *dev_priv)
> if (ret)
> goto err_perf;
>
> - ret = drm_aperture_remove_conflicting_pci_framebuffers(pdev, "inteldrmfb");
> + ret = drm_aperture_remove_conflicting_pci_framebuffers(pdev, "i915drmfb");
> if (ret)
> goto err_ggtt;
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-03 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 13:44 [Intel-gfx] [PATCH] drm/i915: Fix wrong name announced on FB driver switching Janusz Krzysztofik
2021-04-29 19:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-04-29 23:01 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-04-30 8:18 ` Janusz Krzysztofik
2021-05-03 16:22 ` Vudum, Lakshminarayana
2021-05-03 16:04 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2021-05-03 17:38 ` Jani Nikula [this message]
2021-05-13 11:30 ` [Intel-gfx] [PATCH] " Janusz Krzysztofik
2021-05-26 11:32 ` Janusz Krzysztofik
2021-06-01 14:30 ` Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgxbzpiu.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox