From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
airlied@linux.ie, daniel@ffwll.ch, chris@chris-wilson.co.uk
Cc: intel-gfx@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v7 0/4] drm: Move struct drm_device.pdev to legacy
Date: Tue, 27 Apr 2021 15:04:34 +0300 [thread overview]
Message-ID: <87v9883pd9.fsf@intel.com> (raw)
In-Reply-To: <20210427111421.2386-1-tzimmermann@suse.de>
On Tue, 27 Apr 2021, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> V7 of the patchset fixes some bitrot in the intel driver.
>
> The pdev field in struct drm_device points to a PCI device structure and
> goes back to UMS-only days when all DRM drivers were for PCI devices.
> Meanwhile we also support USB, SPI and platform devices. Each of those
> uses the generic device stored in struct drm_device.dev.
>
> To reduce duplication and remove the special case of PCI, this patchset
> converts all modesetting drivers from pdev to dev and makes pdev a field
> for legacy UMS drivers.
>
> For PCI devices, the pointer in struct drm_device.dev can be upcasted to
> struct pci_device; or tested for PCI with dev_is_pci(). In several places
> the code can use the dev field directly.
>
> After converting all drivers and the DRM core, the pdev fields becomes
> only relevant for legacy drivers. In a later patchset, we may want to
> convert these as well and remove pdev entirely.
On the series,
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
How should we merge these?
>
> v7:
> * fix instances of pdev that have benn added under i915/
> v6:
> * also remove assignment in i915/selftests in later patch (Chris)
> v5:
> * remove assignment in later patch (Chris)
> v4:
> * merged several patches
> * moved core changes into separate patch
> * vmwgfx build fix
> v3:
> * merged several patches
> * fix one pdev reference in nouveau (Jeremy)
> * rebases
> v2:
> * move whitespace fixes into separate patches (Alex, Sam)
> * move i915 gt/ and gvt/ changes into separate patches (Joonas)
>
> Thomas Zimmermann (4):
> drm/i915/gt: Remove reference to struct drm_device.pdev
> drm/i915: Remove reference to struct drm_device.pdev
> drm/i915: Don't assign to struct drm_device.pdev
> drm: Move struct drm_device.pdev to legacy section
>
> drivers/gpu/drm/i915/gt/intel_region_lmem.c | 2 +-
> drivers/gpu/drm/i915/i915_drv.c | 1 -
> drivers/gpu/drm/i915/intel_runtime_pm.h | 2 +-
> drivers/gpu/drm/i915/selftests/mock_gem_device.c | 1 -
> include/drm/drm_device.h | 6 +++---
> 5 files changed, 5 insertions(+), 7 deletions(-)
>
> --
> 2.31.1
>
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
airlied@linux.ie, daniel@ffwll.ch, chris@chris-wilson.co.uk
Cc: intel-gfx@lists.freedesktop.org,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v7 0/4] drm: Move struct drm_device.pdev to legacy
Date: Tue, 27 Apr 2021 15:04:34 +0300 [thread overview]
Message-ID: <87v9883pd9.fsf@intel.com> (raw)
In-Reply-To: <20210427111421.2386-1-tzimmermann@suse.de>
On Tue, 27 Apr 2021, Thomas Zimmermann <tzimmermann@suse.de> wrote:
> V7 of the patchset fixes some bitrot in the intel driver.
>
> The pdev field in struct drm_device points to a PCI device structure and
> goes back to UMS-only days when all DRM drivers were for PCI devices.
> Meanwhile we also support USB, SPI and platform devices. Each of those
> uses the generic device stored in struct drm_device.dev.
>
> To reduce duplication and remove the special case of PCI, this patchset
> converts all modesetting drivers from pdev to dev and makes pdev a field
> for legacy UMS drivers.
>
> For PCI devices, the pointer in struct drm_device.dev can be upcasted to
> struct pci_device; or tested for PCI with dev_is_pci(). In several places
> the code can use the dev field directly.
>
> After converting all drivers and the DRM core, the pdev fields becomes
> only relevant for legacy drivers. In a later patchset, we may want to
> convert these as well and remove pdev entirely.
On the series,
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
How should we merge these?
>
> v7:
> * fix instances of pdev that have benn added under i915/
> v6:
> * also remove assignment in i915/selftests in later patch (Chris)
> v5:
> * remove assignment in later patch (Chris)
> v4:
> * merged several patches
> * moved core changes into separate patch
> * vmwgfx build fix
> v3:
> * merged several patches
> * fix one pdev reference in nouveau (Jeremy)
> * rebases
> v2:
> * move whitespace fixes into separate patches (Alex, Sam)
> * move i915 gt/ and gvt/ changes into separate patches (Joonas)
>
> Thomas Zimmermann (4):
> drm/i915/gt: Remove reference to struct drm_device.pdev
> drm/i915: Remove reference to struct drm_device.pdev
> drm/i915: Don't assign to struct drm_device.pdev
> drm: Move struct drm_device.pdev to legacy section
>
> drivers/gpu/drm/i915/gt/intel_region_lmem.c | 2 +-
> drivers/gpu/drm/i915/i915_drv.c | 1 -
> drivers/gpu/drm/i915/intel_runtime_pm.h | 2 +-
> drivers/gpu/drm/i915/selftests/mock_gem_device.c | 1 -
> include/drm/drm_device.h | 6 +++---
> 5 files changed, 5 insertions(+), 7 deletions(-)
>
> --
> 2.31.1
>
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-04-27 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 11:14 [Intel-gfx] [PATCH v7 0/4] drm: Move struct drm_device.pdev to legacy Thomas Zimmermann
2021-04-27 11:14 ` Thomas Zimmermann
2021-04-27 11:14 ` [Intel-gfx] [PATCH v7 1/4] drm/i915/gt: Remove reference to struct drm_device.pdev Thomas Zimmermann
2021-04-27 11:14 ` Thomas Zimmermann
2021-04-27 11:14 ` [Intel-gfx] [PATCH v7 2/4] drm/i915: " Thomas Zimmermann
2021-04-27 11:14 ` Thomas Zimmermann
2021-04-27 11:14 ` [Intel-gfx] [PATCH v7 3/4] drm/i915: Don't assign " Thomas Zimmermann
2021-04-27 11:14 ` Thomas Zimmermann
2021-04-27 11:14 ` [Intel-gfx] [PATCH v7 4/4] drm: Move struct drm_device.pdev to legacy section Thomas Zimmermann
2021-04-27 11:14 ` Thomas Zimmermann
2021-04-27 12:04 ` Jani Nikula [this message]
2021-04-27 12:04 ` [PATCH v7 0/4] drm: Move struct drm_device.pdev to legacy Jani Nikula
2021-04-27 12:10 ` [Intel-gfx] " Thomas Zimmermann
2021-04-27 12:10 ` Thomas Zimmermann
2021-04-27 13:00 ` [Intel-gfx] " Jani Nikula
2021-04-27 13:00 ` Jani Nikula
2021-04-27 13:43 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: Move struct drm_device.pdev to legacy (rev7) Patchwork
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=87v9883pd9.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tzimmermann@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.