All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	feng.tang@intel.com, dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/dp: add module parameter for the dpcd access max retries
Date: Tue, 08 May 2018 22:30:19 +0300	[thread overview]
Message-ID: <878t8uoshg.fsf@intel.com> (raw)
In-Reply-To: <20180508230847.4esu22dtipguqvw3@shbuild888>

On Wed, 09 May 2018, Feng Tang <feng.tang@intel.com> wrote:
>  >> > > > On Mon, May 07, 2018 at 11:40:45AM +0100, Chris Wilson wrote:
>> >> > > > > Quoting Feng Tang (2018-05-07 11:36:09)
>> >> > > > > > To fulfil the Dell 4K monitor, the dpcd max retries has been bumped
>> >> > > > > > from 7 to 32, which may hurt the boot/init time for some platforms,
>> >> > > > > > as the 32 retries may take hundreds of ms.
>> >> > > > >
>> >> > > > > If we need that many retries, so be it. No modparam, the driver just has
>> >> > > > > to work.
>> >> > > >
>> >> > > > I understand your point. The retry numer was originally 7, and worked
>> >> > > > fine untill the Dell 4K monitor which changes to 32.  According to my test,
>> >> > > > each retry will take about 8ms on the A3960 based NUC.
>> >> > > >
>> >> > > > One of our product need to boot up within a given time limit, this
>> >> > > > 32 retries will take about 1/3 of the budget (about 270ms), that's
>> >> > > > why I would try to make it a parameter.
>> >> > >
>> >> > > The essence is that probing whether a monitor is connected should not be
>> >> > > blocking boot. If an async probe tries and fails to find a monitor,
>> >> > > fine - no one will notice. If it does take 270ms to find a monitor, it
>> >> > > turns on 200ms after userspace kicks in, just like any other hotplug.
>> >> >
>> >> > Yeah, the fix here is to get the probing out of the driver load path, not
>> >> > to break the driver for some funky monitors. And definitely not using a
>> >> > modparam.
>> >>
>> >> Hi Chris and Daniel,
>> >>
>> >> After reading the i915 modeset init code, I did some experiments:
>> >> 1. make the intel_modeset_init() function async (here async means
>> >>    creating a async func wrapper and call async_schedul() for it)
>> >> 2. make the intel_setup_outpus()+intel_modeset_setup_hw_state() async
>> >
>> > You could just set i915_pci_driver.driver.prove_type =
>> > PROBE_PREFER_ASYNCHRONOUS for the same result, or set i915.async_probe=1
>> > for testing.
>> >
>> > However, if it's blocking on async_synchronize_full(), that will be no
>> > improvement. So if it is only an existing async_sychronize_full()
>> > causing the fbdev config to be waited on before userspace, we need to
>> > stop using the async mechanism and just use an ordinary worker and
>> > manual flushing. If it's the fbdev probing blocking you, why are you
>> > using fbdev?
>> 
>> Well if it's edp probing, then atm we do need to block since we have
>> no support for panel hotplugging. And userspace generally no
>> expectations that built-in panels come&go. async_synchronize_full
>> making our fbdev code less async than desired is kinda a different
>> story I think here. First step would be trying to figure out why we
>> even bother with edp probing on this platform, when the thing isn't
>> there. Sounds like broken VBT.
>
> Hi Daniel,
>
> Here are some of the VBT and DPCD related logs on my A3900 (bxt + GEN9 LP)
> based NUC. but I don't have the knowledge to tell if the VBT is broken :)

Please run current upstream drm-tip when you're suggesting changes to
upstream code. Looks like you're running at most v4.14. This can't be
emphasized enough. We can't and won't merge the changes unless they make
sense with current code.

As to vbt, please send me /sys/kernel/debug/dri/0/i915_vbt.

BR,
Jani.

>
> [    0.545231] [drm:intel_bios_init] Set default to SSC at 100000 kHz
> [    0.545237] [drm:intel_bios_init] VBT signature "$VBT BROXTON        ", BDB version 207
> [    0.545241] [drm:intel_bios_init] BDB_GENERAL_FEATURES int_tv_support 0 int_crt_support 0 lvds_use_ssc 0 lvds_ssc_freq 120000 display_clock_mode 1 fdi_rx_polarity_inverted 0
> [    0.545245] [drm:intel_bios_init] crt_ddc_bus_pin: 2
> [    0.545255] [drm:intel_opregion_get_panel_type] Failed to get panel details from OpRegion (-19)
> [    0.545257] [drm:intel_bios_init] Panel type: 0 (VBT)
> [    0.545260] [drm:intel_bios_init] DRRS supported mode is seamless
> [    0.545275] [drm:intel_bios_init] Found panel mode in BIOS VBT tables:
> [    0.545281] [drm:drm_mode_debug_printmodeline] Modeline 0:"1920x1080" 0 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x8 0xa
> [    0.545292] [drm:intel_bios_init] VBT backlight PWM modulation frequency 200 Hz, active high, min brightness 0, level 180, controller 1
> [    0.545301] [drm:intel_bios_init] Unsupported child device size for SDVO mapping.
> [    0.545305] [drm:intel_bios_init] Expected child device config size for VBT version 207 not known; assuming 38
> [    0.545323] [drm:intel_bios_init] DRRS State Enabled:1
> [    0.545334] [drm:intel_bios_init] Port A VBT info: DP:1 HDMI:0 DVI:0 EDP:1 CRT:0
> [    0.545338] [drm:intel_bios_init] VBT HDMI level shift for port A: 0
> [    0.545341] [drm:intel_bios_init] Port B VBT info: DP:0 HDMI:1 DVI:1 EDP:0 CRT:0
> [    0.545344] [drm:intel_bios_init] VBT HDMI level shift for port B: 8
> [    0.545347] [drm:intel_bios_init] Port C VBT info: DP:0 HDMI:1 DVI:1 EDP:0 CRT:0
> [    0.545350] [drm:intel_bios_init] VBT HDMI level shift for port C: 8
> [    0.546076] [drm:gen9_set_dc_state] Setting DC state from 00 to 00
> [    0.546091] [drm:intel_power_well_enable] enabling power well 1
> [    0.546126] [drm:gvt_service_thread] gvt: core: service thread start
> [    0.546174] [drm:intel_update_cdclk] Current CD clock rate: 19200 kHz, VCO: 0 kHz, ref: 19200 kHz
> [    0.546176] [drm:bxt_init_cdclk] Sanitizing cdclk programmed by pre-os
> [    0.546339] [drm:intel_update_cdclk] Current CD clock rate: 144000 kHz, VCO: 1152000 kHz, ref: 19200 kHz
> [    0.546357] [drm:intel_power_well_enable] enabling always-on
> [    0.546360] [drm:intel_power_well_enable] enabling DC off
> [    0.546364] [drm:gen9_set_dc_state] Setting DC state from 00 to 00
> [    0.546372] [drm:intel_power_well_enable] enabling power well 2
> [    0.546386] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
> [    0.546396] [drm:intel_power_well_enable] enabling dpio-common-a
> [    0.546488] [drm:intel_power_well_enable] enabling dpio-common-bc
> [    0.546844] [drm:intel_csr_ucode_init] Loading i915/bxt_dmc_ver1_07.bin
> [    0.546854] [drm:drm_irq_install] irq=124
> [    0.546906] i915 0000:00:02.0: Direct firmware load for i915/bxt_dmc_ver1_07.bin failed with error -2
> [    0.546909] i915 0000:00:02.0: Falling back to user helper
> [    0.547098] [drm:__bxt_hpd_detection_setup] Invert bit setting: hp_ctl:18001818 hp_port:38
> [    0.547425] [drm:intel_fbc_init] Sanitized enable_fbc value: 1
> [    0.547445] [drm:intel_print_wm_latency] Gen9 Plane WM0 latency 7 (7.0 usec)
> [    0.547447] [drm:intel_print_wm_latency] Gen9 Plane WM1 latency 7 (7.0 usec)
> [    0.547450] [drm:intel_print_wm_latency] Gen9 Plane WM2 latency 8 (8.0 usec)
> [    0.547453] [drm:intel_print_wm_latency] Gen9 Plane WM3 latency 22 (22.0 usec)
> [    0.547455] [drm:intel_print_wm_latency] Gen9 Plane WM4 latency 22 (22.0 usec)
> [    0.547458] [drm:intel_print_wm_latency] Gen9 Plane WM5 latency 22 (22.0 usec)
> [    0.547460] [drm:intel_print_wm_latency] Gen9 Plane WM6 latency 22 (22.0 usec)
> [    0.547462] [drm:intel_print_wm_latency] Gen9 Plane WM7 latency 22 (22.0 usec)
> [    0.547466] [drm:intel_modeset_init] 3 display pipes available.
> [    0.548182] [drm:intel_update_cdclk] Current CD clock rate: 144000 kHz, VCO: 1152000 kHz, ref: 19200 kHz
> [    0.548393] [drm:intel_update_max_cdclk] Max CD clock rate: 624000 kHz
> [    0.548395] [drm:intel_modeset_init] Max dotclock rate: 624000 kHz
> [    0.549124] [intel_setup_outputs()]: enter
> [    0.549522] [drm:intel_ddi_init] BXT BIOS forgot to set DDI_A_4_LANES for port A; fixing
> [    0.549531] [drm:intel_dp_init_connector] Adding eDP connector on port A
> [    0.549538] [drm:intel_dp_init_connector] using AUX A for port A (VBT)
> [    0.549552] [drm:intel_pps_dump_state] cur t1_t3 0 t8 0 t9 0 t10 0 t11_t12 0
> [    0.549556] [drm:intel_pps_dump_state] vbt t1_t3 2000 t8 10 t9 2000 t10 500 t11_t12 6000
> [    0.549560] [drm:intel_dp_init_panel_power_sequencer.part.19] panel power up delay 200, power down delay 50, power cycle delay 600
> [    0.549563] [drm:intel_dp_init_panel_power_sequencer.part.19] backlight on delay 1, off delay 200
> [    0.549569] [drm:intel_dp_init_panel_power_sequencer_registers] panel power sequencer register settings: PP_ON 0x7d00001, PP_OFF 0x1f40001, PP_DIV 0x60
> [    0.549577] [drm:edp_panel_vdd_on] Turning eDP port A VDD on
> [    0.549580] [drm:wait_panel_power_cycle] Wait for panel power cycle
> [    0.601112] [drm:wait_panel_status] mask b800000f value 00000000 status 00000000 control 00000062
> [    0.601116] [drm:wait_panel_status] Wait complete
> [    0.601121] [drm:edp_panel_vdd_on] PP_STATUS: 0x00000000 PP_CONTROL: 0x0000006a
> [    0.601125] [drm:edp_panel_vdd_on] eDP port A panel power wasn't enabled
> [    0.636720] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.645328] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.653926] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.662531] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.671132] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.679767] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.688366] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.696969] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.705572] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.714173] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.722770] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.731378] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.739983] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.748590] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.757210] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.765808] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.774422] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.783039] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.791642] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.800252] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.808859] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.817481] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.826086] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.834722] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.843335] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.851944] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.860552] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.869160] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.877767] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.886429] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.895045] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.903658] [drm:intel_dp_aux_ch] dp_aux_ch timeout status 0x7d4003ff
> [    0.903665] [drm:drm_dp_dpcd_access] Too many retries, giving up. First error: -110
> [    0.903666] [drm] failed to retrieve link info, disabling eDP
> [    0.903671] [drm:edp_panel_vdd_off_sync] Turning eDP port A VDD off
> [    0.903676] [drm:edp_panel_vdd_off_sync] PP_STATUS: 0x00000000 PP_CONTROL: 0x00000062
> [    0.903695] [drm:intel_hdmi_init_connector] Adding HDMI connector on port B
> [    0.903702] [drm:intel_hdmi_init_connector] Using DDC pin 0x1 for port B (VBT)
> [    0.903720] [drm:intel_hdmi_init_connector] Adding HDMI connector on port C
> [    0.903724] [drm:intel_hdmi_init_connector] Using DDC pin 0x2 for port C (VBT)
> [    0.903728] [drm:intel_dsi_init] 
> [    0.903733] [drm:acrngt_dom0_ready] gvt: core: acrngt: Dom 0 ready to accept Dom U guests
>
> Thanks,
> Feng
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-05-08 19:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 10:36 [PATCH] drm/dp: add module parameter for the dpcd access max retries Feng Tang
2018-05-07 10:40 ` Chris Wilson
2018-05-07 21:26   ` Feng Tang
2018-05-07 13:33     ` Chris Wilson
2018-05-07 15:09       ` Daniel Vetter
2018-05-07 23:19         ` Feng Tang
2018-05-08 19:03         ` Feng Tang
2018-05-08 11:33           ` [Intel-gfx] " Chris Wilson
2018-05-08 12:00             ` Daniel Vetter
2018-05-08 23:08               ` [Intel-gfx] " Feng Tang
2018-05-08 19:30                 ` Jani Nikula [this message]
2018-05-09  6:31                   ` Feng Tang
2018-05-09  7:53                     ` Jani Nikula
2018-05-09  7:56                       ` Feng Tang
2018-05-09  9:28                         ` [Intel-gfx] " Jani Nikula
2018-05-10  9:21                           ` Feng Tang
2018-05-07 11:08 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-05-10  9:33 ` ✗ Fi.CI.BAT: failure for drm/dp: add module parameter for the dpcd access max retries (rev2) 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=878t8uoshg.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=feng.tang@intel.com \
    --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 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.