From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Check for nomodeset in i915_init() first
Date: Mon, 19 Jul 2021 10:37:29 +0100 [thread overview]
Message-ID: <153394a1-2276-313e-7096-e6d18f9ebc61@linux.intel.com> (raw)
In-Reply-To: <ea0ecfbd-6428-02e1-4785-bdf32e475eb8@linux.intel.com>
On 19/07/2021 10:09, Tvrtko Ursulin wrote:
>
> On 19/07/2021 09:35, Daniel Vetter wrote:
>> Jason is trying to sort out the unwinding in i915_init and i915_exit,
>> while reviewing those patches I noticed that we also have the
>> nomodeset handling now in the middle of things.
>>
>> Pull that out for simplisity in unwinding - if you run selftest with
>> nomodeset you get nothing, *shrug*.
>
> Where "nothing" equals success!? Quite bad for platform bringup on two
> levels.
Sorry I confused it with i915.disable_display. I am not aware nomodeset
is actually used anywhere useful so my objection does not hold.
Regards,
Tvrtko
> Regards,
>
> Tvrtko
>
>> Cc: Jason Ekstrand <jason@jlekstrand.net>
>> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_pci.c | 16 ++++++++--------
>> 1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_pci.c
>> b/drivers/gpu/drm/i915/i915_pci.c
>> index 67696d752271..6fe709ac1b4b 100644
>> --- a/drivers/gpu/drm/i915/i915_pci.c
>> +++ b/drivers/gpu/drm/i915/i915_pci.c
>> @@ -1199,14 +1199,6 @@ static int __init i915_init(void)
>> bool use_kms = true;
>> int err;
>> - err = i915_globals_init();
>> - if (err)
>> - return err;
>> -
>> - err = i915_mock_selftests();
>> - if (err)
>> - return err > 0 ? 0 : err;
>> -
>> /*
>> * Enable KMS by default, unless explicitly overriden by
>> * either the i915.modeset prarameter or by the
>> @@ -1225,6 +1217,14 @@ static int __init i915_init(void)
>> return 0;
>> }
>> + err = i915_globals_init();
>> + if (err)
>> + return err;
>> +
>> + err = i915_mock_selftests();
>> + if (err)
>> + return err > 0 ? 0 : err;
>> +
>> i915_pmu_init();
>> err = pci_register_driver(&i915_pci_driver);
>>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-07-19 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 8:35 [Intel-gfx] [PATCH] drm/i915: Check for nomodeset in i915_init() first Daniel Vetter
2021-07-19 9:05 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-07-19 9:09 ` [Intel-gfx] [PATCH] " Tvrtko Ursulin
2021-07-19 9:37 ` Tvrtko Ursulin [this message]
2021-07-19 9:09 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2021-07-19 9:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-19 12:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-07-20 15:53 ` [Intel-gfx] [PATCH] " Jason Ekstrand
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=153394a1-2276-313e-7096-e6d18f9ebc61@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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