From: Jani Nikula <jani.nikula@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915: move intel_display_device_probe() one level higher
Date: Wed, 13 Sep 2023 00:35:19 +0300 [thread overview]
Message-ID: <87v8cfvzvs.fsf@intel.com> (raw)
In-Reply-To: <20230912205720.GM2706891@mdroper-desk1.amr.corp.intel.com>
On Tue, 12 Sep 2023, Matt Roper <matthew.d.roper@intel.com> wrote:
> On Tue, Sep 12, 2023 at 03:05:37PM +0300, Jani Nikula wrote:
>> Don't hide display probe in device info code.
>>
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_driver.c | 2 ++
>> drivers/gpu/drm/i915/intel_device_info.c | 2 --
>> drivers/gpu/drm/i915/selftests/mock_gem_device.c | 2 ++
>> 3 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
>> index f8dbee7a5af7..b5e1f72cc3ce 100644
>> --- a/drivers/gpu/drm/i915/i915_driver.c
>> +++ b/drivers/gpu/drm/i915/i915_driver.c
>> @@ -735,6 +735,8 @@ i915_driver_create(struct pci_dev *pdev, const struct pci_device_id *ent)
>> /* Set up device info and initial runtime info. */
>> intel_device_info_driver_create(i915, pdev->device, match_info);
>>
>> + intel_display_device_probe(i915);
>> +
>> return i915;
>> }
>>
>> diff --git a/drivers/gpu/drm/i915/intel_device_info.c b/drivers/gpu/drm/i915/intel_device_info.c
>> index b9b8b22540cb..d2ed0f057cb2 100644
>> --- a/drivers/gpu/drm/i915/intel_device_info.c
>> +++ b/drivers/gpu/drm/i915/intel_device_info.c
>> @@ -418,8 +418,6 @@ void intel_device_info_driver_create(struct drm_i915_private *i915,
>> runtime = RUNTIME_INFO(i915);
>> memcpy(runtime, &INTEL_INFO(i915)->__runtime, sizeof(*runtime));
>>
>> - intel_display_device_probe(i915);
>> -
>> runtime->device_id = device_id;
>> }
>>
>> diff --git a/drivers/gpu/drm/i915/selftests/mock_gem_device.c b/drivers/gpu/drm/i915/selftests/mock_gem_device.c
>> index da0b269606c5..7de6477803f8 100644
>> --- a/drivers/gpu/drm/i915/selftests/mock_gem_device.c
>> +++ b/drivers/gpu/drm/i915/selftests/mock_gem_device.c
>> @@ -181,6 +181,8 @@ struct drm_i915_private *mock_gem_device(void)
>> /* Set up device info and initial runtime info. */
>> intel_device_info_driver_create(i915, pdev->device, &mock_info);
>>
>> + intel_display_device_probe(i915);
>> +
>
> I realize this call was already happening with the old code, but do we
> really want to be probing the (real) display hardware while setting up
> mock (fake hardware) selftests? I don't think any of the mock tests
> should be doing anything display-related, and if they did we'd probably
> want to add some kind of mock_display_device_probe() instead or using
> the real hardware?
Thought about it, probably not, but decided it should be a separate
patch.
BR,
Jani.
>
>
> Matt
>
>> dev_pm_domain_set(&pdev->dev, &pm_domain);
>> pm_runtime_enable(&pdev->dev);
>> pm_runtime_dont_use_autosuspend(&pdev->dev);
>> --
>> 2.39.2
>>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-09-12 21:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 12:05 [Intel-gfx] [PATCH 1/3] drm/i915: move more of the display probe to display code Jani Nikula
2023-09-12 12:05 ` [Intel-gfx] [PATCH 2/3] drm/i915/display: call gmdid display probe at a higher level Jani Nikula
2023-09-12 12:31 ` Rodrigo Vivi
2023-09-12 12:05 ` [Intel-gfx] [PATCH 3/3] drm/i915: move intel_display_device_probe() one level higher Jani Nikula
2023-09-12 12:32 ` Rodrigo Vivi
2023-09-12 20:57 ` Matt Roper
2023-09-12 21:35 ` Jani Nikula [this message]
2023-09-15 16:39 ` Jani Nikula
2023-09-12 12:31 ` [Intel-gfx] [PATCH 1/3] drm/i915: move more of the display probe to display code Rodrigo Vivi
2023-09-15 15:39 ` Jani Nikula
2023-09-12 19:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] " Patchwork
2023-09-12 20:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-09-12 23:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm/i915: move more of the display probe to display code (rev2) Patchwork
2023-09-12 23:29 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-09-14 22:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm/i915: move more of the display probe to display code (rev3) Patchwork
2023-09-14 23:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-09-15 6:46 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87v8cfvzvs.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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 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.