From: Jani Nikula <jani.nikula@linux.intel.com>
To: mika.kahola@intel.com, "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Return early when pipes are not available
Date: Fri, 10 Nov 2017 15:22:22 +0200 [thread overview]
Message-ID: <87k1yy8e0h.fsf@intel.com> (raw)
In-Reply-To: <1510316521.16370.13.camel@intel.com>
On Fri, 10 Nov 2017, Mika Kahola <mika.kahola@intel.com> wrote:
> On Thu, 2017-11-09 at 15:15 +0200, Ville Syrjälä wrote:
>> On Thu, Nov 09, 2017 at 01:11:05PM +0200, Mika Kahola wrote:
>> >
>> > On Thu, 2017-11-09 at 11:01 +0000, Chris Wilson wrote:
>> > >
>> > > Quoting Mika Kahola (2017-11-09 10:49:52)
>> > > >
>> > > >
>> > > > At least in Coffee Lake it happens that we start initiliazing
>> > > > audio
>> > > > when
>> > > > no display is connected. This was discovered by CI when running
>> > > > IGT
>> > > > test
>> > > > case
>> > > >
>> > > > drv_module_reload --r basic-no-display
>> > > >
>> > > > The issue here is that the 'intel_device_info_runtime_init()'
>> > > > sets
>> > > > num_pipes to 0 but before this happens the audio part has
>> > > > already
>> > > > started
>> > > > to initialize itself. Later on the num_pipes is updated to 0 in
>> > > > intel_device_info_runtime_init() and we hit that when audio
>> > > > part is
>> > > > digging
>> > > > out ELD. This causes a warning in dmesg. To fix this issue,
>> > > > let's
>> > > > check the
>> > > > number of available pipes when trying to read out ELD.
>> > > dev_info_runtime_init() is too late. It depends on mmio being
>> > > enabled
>> > > to
>> > > probe the HW and nothing else; so move it to
>> > > i915_driver_init_mmio()?
>> > Ok. I could try that. I was also thinking that is there a way to
>> > postpone audio initialization?
>> We probably shouldn't be registering the audio thing until we've
>> actually set up the outputs.
> I tried couple of versions. One with Chris's idea to move
> intel_device_info_runtime_init() to i915_driver_init_mmio() didn't turn
> out to be a success.
>
> https://patchwork.freedesktop.org/series/33514/
>
> I also tried to set num_pipes to 0 in case of display disable already
> in i915_driver_init_early(). That approach didn't turn out to be a
> success either.
>
> https://patchwork.freedesktop.org/series/33522/
>
> I'll give it a go for a patch that doesn't register audio in case of
> disabled display.
That seems like the way to go. Display disable on the command line
should be no different from num_pipes == 0.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-10 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 10:49 [PATCH] drm/i915: Return early when pipes are not available Mika Kahola
2017-11-09 11:01 ` Chris Wilson
2017-11-09 11:11 ` Mika Kahola
2017-11-09 13:15 ` Ville Syrjälä
2017-11-10 12:22 ` Mika Kahola
2017-11-10 13:22 ` Jani Nikula [this message]
2017-11-10 13:34 ` Mika Kahola
2017-11-10 13:37 ` Saarinen, Jani
2017-11-09 11:27 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-11-09 12:54 ` ✗ Fi.CI.IGT: failure " 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=87k1yy8e0h.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kahola@intel.com \
--cc=ville.syrjala@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 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.