* [Intel-gfx] [V12 0/4] Add support for mipi dsi cmd mode
@ 2020-09-16 16:15 Vandita Kulkarni
2020-09-16 16:15 ` [Intel-gfx] [V12 1/4] drm/i915/dsi: Add details about TE in get_config Vandita Kulkarni
` (4 more replies)
0 siblings, 5 replies; 10+ messages in thread
From: Vandita Kulkarni @ 2020-09-16 16:15 UTC (permalink / raw)
To: intel-gfx; +Cc: jani.nikula
This series contain interrupt handling part of cmd mode.
Configuration patches were merged already.
v10: Address the review comments on patch 3 and 4
v11: fix compilation issue introduced in v10
v12: fix check patch errors on patch 3
Vandita Kulkarni (4):
drm/i915/dsi: Add details about TE in get_config
i915/dsi: Configure TE interrupt for cmd mode
drm/i915/dsi: Add TE handler for dsi cmd mode.
drm/i915/dsi: Initiate fame request in cmd mode
drivers/gpu/drm/i915/display/icl_dsi.c | 56 +++++++--
drivers/gpu/drm/i915/display/intel_display.c | 10 ++
drivers/gpu/drm/i915/display/intel_dsi.h | 1 +
drivers/gpu/drm/i915/i915_irq.c | 115 ++++++++++++++++++-
4 files changed, 168 insertions(+), 14 deletions(-)
--
2.21.0.5.gaeb582a
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 10+ messages in thread* [Intel-gfx] [V12 1/4] drm/i915/dsi: Add details about TE in get_config 2020-09-16 16:15 [Intel-gfx] [V12 0/4] Add support for mipi dsi cmd mode Vandita Kulkarni @ 2020-09-16 16:15 ` Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 2/4] i915/dsi: Configure TE interrupt for cmd mode Vandita Kulkarni ` (3 subsequent siblings) 4 siblings, 0 replies; 10+ messages in thread From: Vandita Kulkarni @ 2020-09-16 16:15 UTC (permalink / raw) To: intel-gfx; +Cc: jani.nikula We need details about enabling TE on which port before we enable TE through vblank enable path. This is based on the configuration that we receive from the VBT wrt ports, dual_link. Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com> Reviewed-by: Jani Nikula <jani.nikula@intel.com> --- drivers/gpu/drm/i915/display/icl_dsi.c | 30 +++++++++++++++----------- 1 file changed, 18 insertions(+), 12 deletions(-) diff --git a/drivers/gpu/drm/i915/display/icl_dsi.c b/drivers/gpu/drm/i915/display/icl_dsi.c index 520715b7d5b5..2789020e20db 100644 --- a/drivers/gpu/drm/i915/display/icl_dsi.c +++ b/drivers/gpu/drm/i915/display/icl_dsi.c @@ -1447,6 +1447,18 @@ static bool gen11_dsi_is_periodic_cmd_mode(struct intel_dsi *intel_dsi) return (val & DSI_PERIODIC_FRAME_UPDATE_ENABLE); } +static void gen11_dsi_get_cmd_mode_config(struct intel_dsi *intel_dsi, + struct intel_crtc_state *pipe_config) +{ + if (intel_dsi->ports == (BIT(PORT_B) | BIT(PORT_A))) + pipe_config->mode_flags |= I915_MODE_FLAG_DSI_USE_TE1 | + I915_MODE_FLAG_DSI_USE_TE0; + else if (intel_dsi->ports == BIT(PORT_B)) + pipe_config->mode_flags |= I915_MODE_FLAG_DSI_USE_TE1; + else + pipe_config->mode_flags |= I915_MODE_FLAG_DSI_USE_TE0; +} + static void gen11_dsi_get_config(struct intel_encoder *encoder, struct intel_crtc_state *pipe_config) { @@ -1468,6 +1480,10 @@ static void gen11_dsi_get_config(struct intel_encoder *encoder, pipe_config->output_types |= BIT(INTEL_OUTPUT_DSI); pipe_config->pipe_bpp = bdw_get_pipemisc_bpp(crtc); + /* Get the details on which TE should be enabled */ + if (is_cmd_mode(intel_dsi)) + gen11_dsi_get_cmd_mode_config(intel_dsi, pipe_config); + if (gen11_dsi_is_periodic_cmd_mode(intel_dsi)) pipe_config->mode_flags |= I915_MODE_FLAG_DSI_PERIODIC_CMD_MODE; } @@ -1562,18 +1578,8 @@ static int gen11_dsi_compute_config(struct intel_encoder *encoder, * receive TE from the slave if * dual link is enabled */ - if (is_cmd_mode(intel_dsi)) { - if (intel_dsi->ports == (BIT(PORT_B) | BIT(PORT_A))) - pipe_config->mode_flags |= - I915_MODE_FLAG_DSI_USE_TE1 | - I915_MODE_FLAG_DSI_USE_TE0; - else if (intel_dsi->ports == BIT(PORT_B)) - pipe_config->mode_flags |= - I915_MODE_FLAG_DSI_USE_TE1; - else - pipe_config->mode_flags |= - I915_MODE_FLAG_DSI_USE_TE0; - } + if (is_cmd_mode(intel_dsi)) + gen11_dsi_get_cmd_mode_config(intel_dsi, pipe_config); return 0; } -- 2.21.0.5.gaeb582a _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 10+ messages in thread
* [Intel-gfx] [V12 2/4] i915/dsi: Configure TE interrupt for cmd mode 2020-09-16 16:15 [Intel-gfx] [V12 0/4] Add support for mipi dsi cmd mode Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 1/4] drm/i915/dsi: Add details about TE in get_config Vandita Kulkarni @ 2020-09-16 16:15 ` Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 3/4] drm/i915/dsi: Add TE handler for dsi " Vandita Kulkarni ` (2 subsequent siblings) 4 siblings, 0 replies; 10+ messages in thread From: Vandita Kulkarni @ 2020-09-16 16:15 UTC (permalink / raw) To: intel-gfx; +Cc: jani.nikula Configure TE interrupt as part of the vblank enable call flow. v2: Hide the private flags check inside configure_te (Jani) v3: Fix the position of masking de_port_masked for DSI_TE. v4: Simplify the caller of configure_te (Jani) v5: Clear IIR, remove the usage of private_flags v6: including icl_dsi header is not needed Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com> --- drivers/gpu/drm/i915/i915_irq.c | 50 +++++++++++++++++++++++++++++++-- 1 file changed, 48 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c index 759f523c6a6b..913548addfba 100644 --- a/drivers/gpu/drm/i915/i915_irq.c +++ b/drivers/gpu/drm/i915/i915_irq.c @@ -2631,12 +2631,47 @@ int ilk_enable_vblank(struct drm_crtc *crtc) return 0; } +static bool gen11_dsi_configure_te(struct intel_crtc *intel_crtc, + bool enable) +{ + struct drm_i915_private *dev_priv = to_i915(intel_crtc->base.dev); + enum port port; + u32 tmp; + + if (!(intel_crtc->mode_flags & + (I915_MODE_FLAG_DSI_USE_TE1 | I915_MODE_FLAG_DSI_USE_TE0))) + return false; + + /* for dual link cases we consider TE from slave */ + if (intel_crtc->mode_flags & I915_MODE_FLAG_DSI_USE_TE1) + port = PORT_B; + else + port = PORT_A; + + tmp = I915_READ(DSI_INTR_MASK_REG(port)); + if (enable) + tmp &= ~DSI_TE_EVENT; + else + tmp |= DSI_TE_EVENT; + + I915_WRITE(DSI_INTR_MASK_REG(port), tmp); + + tmp = I915_READ(DSI_INTR_IDENT_REG(port)); + I915_WRITE(DSI_INTR_IDENT_REG(port), tmp); + + return true; +} + int bdw_enable_vblank(struct drm_crtc *crtc) { struct drm_i915_private *dev_priv = to_i915(crtc->dev); - enum pipe pipe = to_intel_crtc(crtc)->pipe; + struct intel_crtc *intel_crtc = to_intel_crtc(crtc); + enum pipe pipe = intel_crtc->pipe; unsigned long irqflags; + if (gen11_dsi_configure_te(intel_crtc, true)) + return 0; + spin_lock_irqsave(&dev_priv->irq_lock, irqflags); bdw_enable_pipe_irq(dev_priv, pipe, GEN8_PIPE_VBLANK); spin_unlock_irqrestore(&dev_priv->irq_lock, irqflags); @@ -2702,9 +2737,13 @@ void ilk_disable_vblank(struct drm_crtc *crtc) void bdw_disable_vblank(struct drm_crtc *crtc) { struct drm_i915_private *dev_priv = to_i915(crtc->dev); - enum pipe pipe = to_intel_crtc(crtc)->pipe; + struct intel_crtc *intel_crtc = to_intel_crtc(crtc); + enum pipe pipe = intel_crtc->pipe; unsigned long irqflags; + if (gen11_dsi_configure_te(intel_crtc, false)) + return; + spin_lock_irqsave(&dev_priv->irq_lock, irqflags); bdw_disable_pipe_irq(dev_priv, pipe, GEN8_PIPE_VBLANK); spin_unlock_irqrestore(&dev_priv->irq_lock, irqflags); @@ -3400,6 +3439,13 @@ static void gen8_de_irq_postinstall(struct drm_i915_private *dev_priv) if (IS_GEN9_LP(dev_priv)) de_port_masked |= BXT_DE_PORT_GMBUS; + if (INTEL_GEN(dev_priv) >= 11) { + enum port port; + + if (intel_bios_is_dsi_present(dev_priv, &port)) + de_port_masked |= DSI0_TE | DSI1_TE; + } + de_pipe_enables = de_pipe_masked | GEN8_PIPE_VBLANK | GEN8_PIPE_FIFO_UNDERRUN; -- 2.21.0.5.gaeb582a _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 10+ messages in thread
* [Intel-gfx] [V12 3/4] drm/i915/dsi: Add TE handler for dsi cmd mode. 2020-09-16 16:15 [Intel-gfx] [V12 0/4] Add support for mipi dsi cmd mode Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 1/4] drm/i915/dsi: Add details about TE in get_config Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 2/4] i915/dsi: Configure TE interrupt for cmd mode Vandita Kulkarni @ 2020-09-16 16:15 ` Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in " Vandita Kulkarni 2020-09-16 17:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Add support for mipi dsi cmd mode (rev12) Patchwork 4 siblings, 0 replies; 10+ messages in thread From: Vandita Kulkarni @ 2020-09-16 16:15 UTC (permalink / raw) To: intel-gfx; +Cc: jani.nikula In case of dual link, we get the TE on slave. So clear the TE on slave DSI IIR. If we are operating in TE_GATE mode, after we do a frame update, the transcoder will send the frame data to the panel, after it receives a TE. Whereas if we are operating in NO_GATE mode then the transcoder will immediately send the frame data to the panel. We are not dealing with the periodic command mode here. v2: Pass only relevant masked bits to the handler (Jani) v3: Fix the check for cmd mode in TE handler function. v4: Use intel_handle_vblank instead of drm_handle_vblank (Jani) v3: Use static on handler func (Jani) Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com> Reported-by: kernel test robot <lkp@intel.com> Acked-by: Jani Nikula <jani.nikula@intel.com> --- drivers/gpu/drm/i915/i915_irq.c | 65 +++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+) diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c index 913548addfba..c2e4b227bdf3 100644 --- a/drivers/gpu/drm/i915/i915_irq.c +++ b/drivers/gpu/drm/i915/i915_irq.c @@ -2237,6 +2237,63 @@ gen8_de_misc_irq_handler(struct drm_i915_private *dev_priv, u32 iir) drm_err(&dev_priv->drm, "Unexpected DE Misc interrupt\n"); } +static void gen11_dsi_te_interrupt_handler(struct drm_i915_private *dev_priv, + u32 te_trigger) +{ + enum pipe pipe = INVALID_PIPE; + enum transcoder dsi_trans; + enum port port; + u32 val, tmp; + + /* + * Incase of dual link, TE comes from DSI_1 + * this is to check if dual link is enabled + */ + val = I915_READ(TRANS_DDI_FUNC_CTL2(TRANSCODER_DSI_0)); + val &= PORT_SYNC_MODE_ENABLE; + + /* + * if dual link is enabled, then read DSI_0 + * transcoder registers + */ + port = ((te_trigger & DSI1_TE && val) || (te_trigger & DSI0_TE)) ? + PORT_A : PORT_B; + dsi_trans = (port == PORT_A) ? TRANSCODER_DSI_0 : TRANSCODER_DSI_1; + + /* Check if DSI configured in command mode */ + val = I915_READ(DSI_TRANS_FUNC_CONF(dsi_trans)); + val = val & OP_MODE_MASK; + + if (val != CMD_MODE_NO_GATE && val != CMD_MODE_TE_GATE) { + drm_err(&dev_priv->drm, "DSI trancoder not configured in command mode\n"); + return; + } + + /* Get PIPE for handling VBLANK event */ + val = I915_READ(TRANS_DDI_FUNC_CTL(dsi_trans)); + switch (val & TRANS_DDI_EDP_INPUT_MASK) { + case TRANS_DDI_EDP_INPUT_A_ON: + pipe = PIPE_A; + break; + case TRANS_DDI_EDP_INPUT_B_ONOFF: + pipe = PIPE_B; + break; + case TRANS_DDI_EDP_INPUT_C_ONOFF: + pipe = PIPE_C; + break; + default: + drm_err(&dev_priv->drm, "Invalid PIPE\n"); + return; + } + + intel_handle_vblank(dev_priv, pipe); + + /* clear TE in dsi IIR */ + port = (te_trigger & DSI1_TE) ? PORT_B : PORT_A; + tmp = I915_READ(DSI_INTR_IDENT_REG(port)); + I915_WRITE(DSI_INTR_IDENT_REG(port), tmp); +} + static irqreturn_t gen8_de_irq_handler(struct drm_i915_private *dev_priv, u32 master_ctl) { @@ -2301,6 +2358,14 @@ gen8_de_irq_handler(struct drm_i915_private *dev_priv, u32 master_ctl) found = true; } + if (INTEL_GEN(dev_priv) >= 11) { + tmp_mask = iir & (DSI0_TE | DSI1_TE); + if (tmp_mask) { + gen11_dsi_te_interrupt_handler(dev_priv, tmp_mask); + found = true; + } + } + if (!found) drm_err(&dev_priv->drm, "Unexpected DE Port interrupt\n"); -- 2.21.0.5.gaeb582a _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 10+ messages in thread
* [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in cmd mode 2020-09-16 16:15 [Intel-gfx] [V12 0/4] Add support for mipi dsi cmd mode Vandita Kulkarni ` (2 preceding siblings ...) 2020-09-16 16:15 ` [Intel-gfx] [V12 3/4] drm/i915/dsi: Add TE handler for dsi " Vandita Kulkarni @ 2020-09-16 16:15 ` Vandita Kulkarni 2020-09-17 11:31 ` Ville Syrjälä 2020-09-16 17:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Add support for mipi dsi cmd mode (rev12) Patchwork 4 siblings, 1 reply; 10+ messages in thread From: Vandita Kulkarni @ 2020-09-16 16:15 UTC (permalink / raw) To: intel-gfx; +Cc: jani.nikula In TE Gate mode or TE NO_GATE mode on every flip we need to set the frame update request bit. After this bit is set transcoder hardware will automatically send the frame data to the panel in case of TE NO_GATE mode, where it sends after it receives the TE event in case of TE_GATE mode. Once the frame data is sent to the panel, we see the frame counter updating. v2: Use intel_de_read/write v3: remove the usage of private_flags v4: Use icl_dsi in func names if non static, fix code formatting issues. (Jani) Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com> --- drivers/gpu/drm/i915/display/icl_dsi.c | 26 ++++++++++++++++++++ drivers/gpu/drm/i915/display/intel_display.c | 10 ++++++++ drivers/gpu/drm/i915/display/intel_dsi.h | 1 + 3 files changed, 37 insertions(+) diff --git a/drivers/gpu/drm/i915/display/icl_dsi.c b/drivers/gpu/drm/i915/display/icl_dsi.c index 2789020e20db..7d2abc7f6ba3 100644 --- a/drivers/gpu/drm/i915/display/icl_dsi.c +++ b/drivers/gpu/drm/i915/display/icl_dsi.c @@ -205,6 +205,32 @@ static int dsi_send_pkt_payld(struct intel_dsi_host *host, return 0; } +void icl_dsi_frame_update(struct intel_crtc_state *crtc_state) +{ + struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc); + struct drm_i915_private *dev_priv = to_i915(crtc->base.dev); + u32 tmp, flags; + enum port port; + + flags = crtc->mode_flags; + + /* + * case 1 also covers dual link + * In case of dual link, frame update should be set on + * DSI_0 + */ + if (flags & I915_MODE_FLAG_DSI_USE_TE0) + port = PORT_A; + else if (flags & I915_MODE_FLAG_DSI_USE_TE1) + port = PORT_B; + else + return; + + tmp = intel_de_read(dev_priv, DSI_CMD_FRMCTL(port)); + tmp |= DSI_FRAME_UPDATE_REQUEST; + intel_de_write(dev_priv, DSI_CMD_FRMCTL(port), tmp); +} + static void dsi_program_swing_and_deemphasis(struct intel_encoder *encoder) { struct drm_i915_private *dev_priv = to_i915(encoder->base.dev); diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c index f862403388f6..11a20bf2255f 100644 --- a/drivers/gpu/drm/i915/display/intel_display.c +++ b/drivers/gpu/drm/i915/display/intel_display.c @@ -15621,6 +15621,16 @@ static void intel_atomic_commit_tail(struct intel_atomic_state *state) intel_set_cdclk_post_plane_update(state); } + /* + * Incase of mipi dsi command mode, we need to set frame update + * for every commit + */ + for_each_new_intel_crtc_in_state(state, crtc, new_crtc_state, i) + if (INTEL_GEN(dev_priv) >= 11 && + intel_crtc_has_type(new_crtc_state, INTEL_OUTPUT_DSI)) + if (new_crtc_state->hw.active) + icl_dsi_frame_update(new_crtc_state); + /* FIXME: We should call drm_atomic_helper_commit_hw_done() here * already, but still need the state for the delayed optimization. To * fix this: diff --git a/drivers/gpu/drm/i915/display/intel_dsi.h b/drivers/gpu/drm/i915/display/intel_dsi.h index 19f78a4022d3..625f2f1ae061 100644 --- a/drivers/gpu/drm/i915/display/intel_dsi.h +++ b/drivers/gpu/drm/i915/display/intel_dsi.h @@ -167,6 +167,7 @@ static inline u16 intel_dsi_encoder_ports(struct intel_encoder *encoder) /* icl_dsi.c */ void icl_dsi_init(struct drm_i915_private *dev_priv); +void icl_dsi_frame_update(struct intel_crtc_state *crtc_state); /* intel_dsi.c */ int intel_dsi_bitrate(const struct intel_dsi *intel_dsi); -- 2.21.0.5.gaeb582a _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in cmd mode 2020-09-16 16:15 ` [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in " Vandita Kulkarni @ 2020-09-17 11:31 ` Ville Syrjälä 2020-09-17 11:56 ` Kulkarni, Vandita 0 siblings, 1 reply; 10+ messages in thread From: Ville Syrjälä @ 2020-09-17 11:31 UTC (permalink / raw) To: Vandita Kulkarni; +Cc: jani.nikula, intel-gfx On Wed, Sep 16, 2020 at 09:45:28PM +0530, Vandita Kulkarni wrote: > In TE Gate mode or TE NO_GATE mode on every flip > we need to set the frame update request bit. > After this bit is set transcoder hardware will > automatically send the frame data to the panel > in case of TE NO_GATE mode, where it sends after > it receives the TE event in case of TE_GATE mode. > Once the frame data is sent to the panel, we see > the frame counter updating. > > v2: Use intel_de_read/write > > v3: remove the usage of private_flags > > v4: Use icl_dsi in func names if non static, > fix code formatting issues. (Jani) > > Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com> > --- > drivers/gpu/drm/i915/display/icl_dsi.c | 26 ++++++++++++++++++++ > drivers/gpu/drm/i915/display/intel_display.c | 10 ++++++++ > drivers/gpu/drm/i915/display/intel_dsi.h | 1 + > 3 files changed, 37 insertions(+) > > diff --git a/drivers/gpu/drm/i915/display/icl_dsi.c b/drivers/gpu/drm/i915/display/icl_dsi.c > index 2789020e20db..7d2abc7f6ba3 100644 > --- a/drivers/gpu/drm/i915/display/icl_dsi.c > +++ b/drivers/gpu/drm/i915/display/icl_dsi.c > @@ -205,6 +205,32 @@ static int dsi_send_pkt_payld(struct intel_dsi_host *host, > return 0; > } > > +void icl_dsi_frame_update(struct intel_crtc_state *crtc_state) > +{ > + struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc); > + struct drm_i915_private *dev_priv = to_i915(crtc->base.dev); > + u32 tmp, flags; > + enum port port; > + > + flags = crtc->mode_flags; > + > + /* > + * case 1 also covers dual link > + * In case of dual link, frame update should be set on > + * DSI_0 > + */ > + if (flags & I915_MODE_FLAG_DSI_USE_TE0) > + port = PORT_A; > + else if (flags & I915_MODE_FLAG_DSI_USE_TE1) > + port = PORT_B; > + else > + return; > + > + tmp = intel_de_read(dev_priv, DSI_CMD_FRMCTL(port)); > + tmp |= DSI_FRAME_UPDATE_REQUEST; > + intel_de_write(dev_priv, DSI_CMD_FRMCTL(port), tmp); > +} > + > static void dsi_program_swing_and_deemphasis(struct intel_encoder *encoder) > { > struct drm_i915_private *dev_priv = to_i915(encoder->base.dev); > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c > index f862403388f6..11a20bf2255f 100644 > --- a/drivers/gpu/drm/i915/display/intel_display.c > +++ b/drivers/gpu/drm/i915/display/intel_display.c > @@ -15621,6 +15621,16 @@ static void intel_atomic_commit_tail(struct intel_atomic_state *state) > intel_set_cdclk_post_plane_update(state); > } > > + /* > + * Incase of mipi dsi command mode, we need to set frame update > + * for every commit > + */ > + for_each_new_intel_crtc_in_state(state, crtc, new_crtc_state, i) > + if (INTEL_GEN(dev_priv) >= 11 && > + intel_crtc_has_type(new_crtc_state, INTEL_OUTPUT_DSI)) > + if (new_crtc_state->hw.active) > + icl_dsi_frame_update(new_crtc_state); If this is the thing that triggers the update then it should probably be called at the start of intel_pipe_update_end(). > + > /* FIXME: We should call drm_atomic_helper_commit_hw_done() here > * already, but still need the state for the delayed optimization. To > * fix this: > diff --git a/drivers/gpu/drm/i915/display/intel_dsi.h b/drivers/gpu/drm/i915/display/intel_dsi.h > index 19f78a4022d3..625f2f1ae061 100644 > --- a/drivers/gpu/drm/i915/display/intel_dsi.h > +++ b/drivers/gpu/drm/i915/display/intel_dsi.h > @@ -167,6 +167,7 @@ static inline u16 intel_dsi_encoder_ports(struct intel_encoder *encoder) > > /* icl_dsi.c */ > void icl_dsi_init(struct drm_i915_private *dev_priv); > +void icl_dsi_frame_update(struct intel_crtc_state *crtc_state); > > /* intel_dsi.c */ > int intel_dsi_bitrate(const struct intel_dsi *intel_dsi); > -- > 2.21.0.5.gaeb582a -- Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in cmd mode 2020-09-17 11:31 ` Ville Syrjälä @ 2020-09-17 11:56 ` Kulkarni, Vandita 2020-09-17 12:37 ` Ville Syrjälä 0 siblings, 1 reply; 10+ messages in thread From: Kulkarni, Vandita @ 2020-09-17 11:56 UTC (permalink / raw) To: Ville Syrjälä; +Cc: Nikula, Jani, intel-gfx@lists.freedesktop.org > -----Original Message----- > From: Ville Syrjälä <ville.syrjala@linux.intel.com> > Sent: Thursday, September 17, 2020 5:01 PM > To: Kulkarni, Vandita <vandita.kulkarni@intel.com> > Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani <jani.nikula@intel.com>; B S, > Karthik <karthik.b.s@intel.com> > Subject: Re: [V12 4/4] drm/i915/dsi: Initiate fame request in cmd mode > > On Wed, Sep 16, 2020 at 09:45:28PM +0530, Vandita Kulkarni wrote: > > In TE Gate mode or TE NO_GATE mode on every flip we need to set the > > frame update request bit. > > After this bit is set transcoder hardware will automatically send the > > frame data to the panel in case of TE NO_GATE mode, where it sends > > after it receives the TE event in case of TE_GATE mode. > > Once the frame data is sent to the panel, we see the frame counter > > updating. > > > > v2: Use intel_de_read/write > > > > v3: remove the usage of private_flags > > > > v4: Use icl_dsi in func names if non static, > > fix code formatting issues. (Jani) > > > > Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com> > > --- > > drivers/gpu/drm/i915/display/icl_dsi.c | 26 ++++++++++++++++++++ > > drivers/gpu/drm/i915/display/intel_display.c | 10 ++++++++ > > drivers/gpu/drm/i915/display/intel_dsi.h | 1 + > > 3 files changed, 37 insertions(+) > > > > diff --git a/drivers/gpu/drm/i915/display/icl_dsi.c > > b/drivers/gpu/drm/i915/display/icl_dsi.c > > index 2789020e20db..7d2abc7f6ba3 100644 > > --- a/drivers/gpu/drm/i915/display/icl_dsi.c > > +++ b/drivers/gpu/drm/i915/display/icl_dsi.c > > @@ -205,6 +205,32 @@ static int dsi_send_pkt_payld(struct intel_dsi_host > *host, > > return 0; > > } > > > > +void icl_dsi_frame_update(struct intel_crtc_state *crtc_state) { > > + struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc); > > + struct drm_i915_private *dev_priv = to_i915(crtc->base.dev); > > + u32 tmp, flags; > > + enum port port; > > + > > + flags = crtc->mode_flags; > > + > > + /* > > + * case 1 also covers dual link > > + * In case of dual link, frame update should be set on > > + * DSI_0 > > + */ > > + if (flags & I915_MODE_FLAG_DSI_USE_TE0) > > + port = PORT_A; > > + else if (flags & I915_MODE_FLAG_DSI_USE_TE1) > > + port = PORT_B; > > + else > > + return; > > + > > + tmp = intel_de_read(dev_priv, DSI_CMD_FRMCTL(port)); > > + tmp |= DSI_FRAME_UPDATE_REQUEST; > > + intel_de_write(dev_priv, DSI_CMD_FRMCTL(port), tmp); } > > + > > static void dsi_program_swing_and_deemphasis(struct intel_encoder > > *encoder) { > > struct drm_i915_private *dev_priv = to_i915(encoder->base.dev); > diff > > --git a/drivers/gpu/drm/i915/display/intel_display.c > > b/drivers/gpu/drm/i915/display/intel_display.c > > index f862403388f6..11a20bf2255f 100644 > > --- a/drivers/gpu/drm/i915/display/intel_display.c > > +++ b/drivers/gpu/drm/i915/display/intel_display.c > > @@ -15621,6 +15621,16 @@ static void intel_atomic_commit_tail(struct > intel_atomic_state *state) > > intel_set_cdclk_post_plane_update(state); > > } > > > > + /* > > + * Incase of mipi dsi command mode, we need to set frame update > > + * for every commit > > + */ > > + for_each_new_intel_crtc_in_state(state, crtc, new_crtc_state, i) > > + if (INTEL_GEN(dev_priv) >= 11 && > > + intel_crtc_has_type(new_crtc_state, INTEL_OUTPUT_DSI)) > > + if (new_crtc_state->hw.active) > > + icl_dsi_frame_update(new_crtc_state); > > If this is the thing that triggers the update then it should probably be called at > the start of intel_pipe_update_end(). I could move it to the end of intel_pipe_update_end, as we need TE to be enabled. Because if the frame updates are gated then, the dsi controller will not drive the vblank/ frame start to the display engine until it receives a TE in the presence of the frame update request. And if we are in non gated mode then the dsi controller will immediately drive the vblank/frame strart as soon as it receives the frame update request. So is it ok if I move it to the end of pipe_update_end.. Thanks, Vandita > > > + > > /* FIXME: We should call drm_atomic_helper_commit_hw_done() > here > > * already, but still need the state for the delayed optimization. To > > * fix this: > > diff --git a/drivers/gpu/drm/i915/display/intel_dsi.h > > b/drivers/gpu/drm/i915/display/intel_dsi.h > > index 19f78a4022d3..625f2f1ae061 100644 > > --- a/drivers/gpu/drm/i915/display/intel_dsi.h > > +++ b/drivers/gpu/drm/i915/display/intel_dsi.h > > @@ -167,6 +167,7 @@ static inline u16 intel_dsi_encoder_ports(struct > > intel_encoder *encoder) > > > > /* icl_dsi.c */ > > void icl_dsi_init(struct drm_i915_private *dev_priv); > > +void icl_dsi_frame_update(struct intel_crtc_state *crtc_state); > > > > /* intel_dsi.c */ > > int intel_dsi_bitrate(const struct intel_dsi *intel_dsi); > > -- > > 2.21.0.5.gaeb582a > > -- > Ville Syrjälä > Intel _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in cmd mode 2020-09-17 11:56 ` Kulkarni, Vandita @ 2020-09-17 12:37 ` Ville Syrjälä 2020-09-17 13:01 ` Kulkarni, Vandita 0 siblings, 1 reply; 10+ messages in thread From: Ville Syrjälä @ 2020-09-17 12:37 UTC (permalink / raw) To: Kulkarni, Vandita; +Cc: Nikula, Jani, intel-gfx@lists.freedesktop.org On Thu, Sep 17, 2020 at 11:56:44AM +0000, Kulkarni, Vandita wrote: > > -----Original Message----- > > From: Ville Syrjälä <ville.syrjala@linux.intel.com> > > Sent: Thursday, September 17, 2020 5:01 PM > > To: Kulkarni, Vandita <vandita.kulkarni@intel.com> > > Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani <jani.nikula@intel.com>; B S, > > Karthik <karthik.b.s@intel.com> > > Subject: Re: [V12 4/4] drm/i915/dsi: Initiate fame request in cmd mode > > > > On Wed, Sep 16, 2020 at 09:45:28PM +0530, Vandita Kulkarni wrote: > > > In TE Gate mode or TE NO_GATE mode on every flip we need to set the > > > frame update request bit. > > > After this bit is set transcoder hardware will automatically send the > > > frame data to the panel in case of TE NO_GATE mode, where it sends > > > after it receives the TE event in case of TE_GATE mode. > > > Once the frame data is sent to the panel, we see the frame counter > > > updating. > > > > > > v2: Use intel_de_read/write > > > > > > v3: remove the usage of private_flags > > > > > > v4: Use icl_dsi in func names if non static, > > > fix code formatting issues. (Jani) > > > > > > Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com> > > > --- > > > drivers/gpu/drm/i915/display/icl_dsi.c | 26 ++++++++++++++++++++ > > > drivers/gpu/drm/i915/display/intel_display.c | 10 ++++++++ > > > drivers/gpu/drm/i915/display/intel_dsi.h | 1 + > > > 3 files changed, 37 insertions(+) > > > > > > diff --git a/drivers/gpu/drm/i915/display/icl_dsi.c > > > b/drivers/gpu/drm/i915/display/icl_dsi.c > > > index 2789020e20db..7d2abc7f6ba3 100644 > > > --- a/drivers/gpu/drm/i915/display/icl_dsi.c > > > +++ b/drivers/gpu/drm/i915/display/icl_dsi.c > > > @@ -205,6 +205,32 @@ static int dsi_send_pkt_payld(struct intel_dsi_host > > *host, > > > return 0; > > > } > > > > > > +void icl_dsi_frame_update(struct intel_crtc_state *crtc_state) { > > > + struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc); > > > + struct drm_i915_private *dev_priv = to_i915(crtc->base.dev); > > > + u32 tmp, flags; > > > + enum port port; > > > + > > > + flags = crtc->mode_flags; > > > + > > > + /* > > > + * case 1 also covers dual link > > > + * In case of dual link, frame update should be set on > > > + * DSI_0 > > > + */ > > > + if (flags & I915_MODE_FLAG_DSI_USE_TE0) > > > + port = PORT_A; > > > + else if (flags & I915_MODE_FLAG_DSI_USE_TE1) > > > + port = PORT_B; > > > + else > > > + return; > > > + > > > + tmp = intel_de_read(dev_priv, DSI_CMD_FRMCTL(port)); > > > + tmp |= DSI_FRAME_UPDATE_REQUEST; > > > + intel_de_write(dev_priv, DSI_CMD_FRMCTL(port), tmp); } > > > + > > > static void dsi_program_swing_and_deemphasis(struct intel_encoder > > > *encoder) { > > > struct drm_i915_private *dev_priv = to_i915(encoder->base.dev); > > diff > > > --git a/drivers/gpu/drm/i915/display/intel_display.c > > > b/drivers/gpu/drm/i915/display/intel_display.c > > > index f862403388f6..11a20bf2255f 100644 > > > --- a/drivers/gpu/drm/i915/display/intel_display.c > > > +++ b/drivers/gpu/drm/i915/display/intel_display.c > > > @@ -15621,6 +15621,16 @@ static void intel_atomic_commit_tail(struct > > intel_atomic_state *state) > > > intel_set_cdclk_post_plane_update(state); > > > } > > > > > > + /* > > > + * Incase of mipi dsi command mode, we need to set frame update > > > + * for every commit > > > + */ > > > + for_each_new_intel_crtc_in_state(state, crtc, new_crtc_state, i) > > > + if (INTEL_GEN(dev_priv) >= 11 && > > > + intel_crtc_has_type(new_crtc_state, INTEL_OUTPUT_DSI)) > > > + if (new_crtc_state->hw.active) > > > + icl_dsi_frame_update(new_crtc_state); > > > > If this is the thing that triggers the update then it should probably be called at > > the start of intel_pipe_update_end(). > > I could move it to the end of intel_pipe_update_end, as we need TE to be enabled. > Because if the frame updates are gated then, the dsi controller will not drive the vblank/ frame start to the display engine > until it receives a TE in the presence of the frame update request. > And if we are in non gated mode then the dsi controller will immediately drive the vblank/frame strart as soon as it receives the > frame update request. > > So is it ok if I move it to the end of pipe_update_end.. Sounds racy. Though TBH I can't tell whether the we'd still fire off the event at the right time if we kick the update at the start. Once kicked, is the frame upload going to wait for the TE and then try to stay ahead of the raster beam? -- Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in cmd mode 2020-09-17 12:37 ` Ville Syrjälä @ 2020-09-17 13:01 ` Kulkarni, Vandita 0 siblings, 0 replies; 10+ messages in thread From: Kulkarni, Vandita @ 2020-09-17 13:01 UTC (permalink / raw) To: Ville Syrjälä; +Cc: Nikula, Jani, intel-gfx@lists.freedesktop.org > -----Original Message----- > From: Ville Syrjälä <ville.syrjala@linux.intel.com> > Sent: Thursday, September 17, 2020 6:08 PM > To: Kulkarni, Vandita <vandita.kulkarni@intel.com> > Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani <jani.nikula@intel.com>; B S, > Karthik <karthik.b.s@intel.com> > Subject: Re: [V12 4/4] drm/i915/dsi: Initiate fame request in cmd mode > > On Thu, Sep 17, 2020 at 11:56:44AM +0000, Kulkarni, Vandita wrote: > > > -----Original Message----- > > > From: Ville Syrjälä <ville.syrjala@linux.intel.com> > > > Sent: Thursday, September 17, 2020 5:01 PM > > > To: Kulkarni, Vandita <vandita.kulkarni@intel.com> > > > Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani > > > <jani.nikula@intel.com>; B S, Karthik <karthik.b.s@intel.com> > > > Subject: Re: [V12 4/4] drm/i915/dsi: Initiate fame request in cmd > > > mode > > > > > > On Wed, Sep 16, 2020 at 09:45:28PM +0530, Vandita Kulkarni wrote: > > > > In TE Gate mode or TE NO_GATE mode on every flip we need to set > > > > the frame update request bit. > > > > After this bit is set transcoder hardware will automatically send > > > > the frame data to the panel in case of TE NO_GATE mode, where it > > > > sends after it receives the TE event in case of TE_GATE mode. > > > > Once the frame data is sent to the panel, we see the frame counter > > > > updating. > > > > > > > > v2: Use intel_de_read/write > > > > > > > > v3: remove the usage of private_flags > > > > > > > > v4: Use icl_dsi in func names if non static, > > > > fix code formatting issues. (Jani) > > > > > > > > Signed-off-by: Vandita Kulkarni <vandita.kulkarni@intel.com> > > > > --- > > > > drivers/gpu/drm/i915/display/icl_dsi.c | 26 > ++++++++++++++++++++ > > > > drivers/gpu/drm/i915/display/intel_display.c | 10 ++++++++ > > > > drivers/gpu/drm/i915/display/intel_dsi.h | 1 + > > > > 3 files changed, 37 insertions(+) > > > > > > > > diff --git a/drivers/gpu/drm/i915/display/icl_dsi.c > > > > b/drivers/gpu/drm/i915/display/icl_dsi.c > > > > index 2789020e20db..7d2abc7f6ba3 100644 > > > > --- a/drivers/gpu/drm/i915/display/icl_dsi.c > > > > +++ b/drivers/gpu/drm/i915/display/icl_dsi.c > > > > @@ -205,6 +205,32 @@ static int dsi_send_pkt_payld(struct > > > > intel_dsi_host > > > *host, > > > > return 0; > > > > } > > > > > > > > +void icl_dsi_frame_update(struct intel_crtc_state *crtc_state) { > > > > + struct intel_crtc *crtc = to_intel_crtc(crtc_state->uapi.crtc); > > > > + struct drm_i915_private *dev_priv = to_i915(crtc->base.dev); > > > > + u32 tmp, flags; > > > > + enum port port; > > > > + > > > > + flags = crtc->mode_flags; > > > > + > > > > + /* > > > > + * case 1 also covers dual link > > > > + * In case of dual link, frame update should be set on > > > > + * DSI_0 > > > > + */ > > > > + if (flags & I915_MODE_FLAG_DSI_USE_TE0) > > > > + port = PORT_A; > > > > + else if (flags & I915_MODE_FLAG_DSI_USE_TE1) > > > > + port = PORT_B; > > > > + else > > > > + return; > > > > + > > > > + tmp = intel_de_read(dev_priv, DSI_CMD_FRMCTL(port)); > > > > + tmp |= DSI_FRAME_UPDATE_REQUEST; > > > > + intel_de_write(dev_priv, DSI_CMD_FRMCTL(port), tmp); } > > > > + > > > > static void dsi_program_swing_and_deemphasis(struct intel_encoder > > > > *encoder) { > > > > struct drm_i915_private *dev_priv = to_i915(encoder->base.dev); > > > diff > > > > --git a/drivers/gpu/drm/i915/display/intel_display.c > > > > b/drivers/gpu/drm/i915/display/intel_display.c > > > > index f862403388f6..11a20bf2255f 100644 > > > > --- a/drivers/gpu/drm/i915/display/intel_display.c > > > > +++ b/drivers/gpu/drm/i915/display/intel_display.c > > > > @@ -15621,6 +15621,16 @@ static void > > > > intel_atomic_commit_tail(struct > > > intel_atomic_state *state) > > > > intel_set_cdclk_post_plane_update(state); > > > > } > > > > > > > > + /* > > > > + * Incase of mipi dsi command mode, we need to set frame update > > > > + * for every commit > > > > + */ > > > > + for_each_new_intel_crtc_in_state(state, crtc, new_crtc_state, i) > > > > + if (INTEL_GEN(dev_priv) >= 11 && > > > > + intel_crtc_has_type(new_crtc_state, INTEL_OUTPUT_DSI)) > > > > + if (new_crtc_state->hw.active) > > > > + icl_dsi_frame_update(new_crtc_state); > > > > > > If this is the thing that triggers the update then it should > > > probably be called at the start of intel_pipe_update_end(). > > > > I could move it to the end of intel_pipe_update_end, as we need TE to be > enabled. > > Because if the frame updates are gated then, the dsi controller will > > not drive the vblank/ frame start to the display engine until it receives a TE > in the presence of the frame update request. > > And if we are in non gated mode then the dsi controller will > > immediately drive the vblank/frame strart as soon as it receives the frame > update request. > > > > So is it ok if I move it to the end of pipe_update_end.. > > Sounds racy. Though TBH I can't tell whether the we'd still fire off the event > at the right time if we kick the update at the start. > Once kicked, is the frame upload going to wait for the TE and then try to stay > ahead of the raster beam? In case of TE gate mode it waits for TE before starting memory writes to the periphery. So if we add this at the end of pipe_update, then we would have enabled the TE( as part of vblank enable call) Then we do a frame update eg TE gate mode We wait for 1 TE Then we get another TE in which we can see that the frame counter is incremented. And only now we would be able to send the Vblank event to the user space. In the earlier TE we would not have sent the event as the frame counter couldn't have updated. This is the workflow that is expected in case of TE gate mode. I didn't get the race part, do you mean to say that the wait for TE duration need not be same always? Because we could send the frame update any time? Thanks, Vandita > > -- > Ville Syrjälä > Intel _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for Add support for mipi dsi cmd mode (rev12) 2020-09-16 16:15 [Intel-gfx] [V12 0/4] Add support for mipi dsi cmd mode Vandita Kulkarni ` (3 preceding siblings ...) 2020-09-16 16:15 ` [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in " Vandita Kulkarni @ 2020-09-16 17:10 ` Patchwork 4 siblings, 0 replies; 10+ messages in thread From: Patchwork @ 2020-09-16 17:10 UTC (permalink / raw) To: Vandita Kulkarni; +Cc: intel-gfx [-- Attachment #1.1: Type: text/plain, Size: 9232 bytes --] == Series Details == Series: Add support for mipi dsi cmd mode (rev12) URL : https://patchwork.freedesktop.org/series/69290/ State : success == Summary == CI Bug Log - changes from CI_DRM_9019 -> Patchwork_18514 ==================================================== Summary ------- **WARNING** Minor unknown changes coming with Patchwork_18514 need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_18514, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/index.html Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_18514: ### IGT changes ### #### Warnings #### * igt@i915_selftest@live@gt_lrc: - fi-tgl-y: [DMESG-FAIL][1] ([i915#2373]) -> [DMESG-FAIL][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-tgl-y/igt@i915_selftest@live@gt_lrc.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-tgl-y/igt@i915_selftest@live@gt_lrc.html Known issues ------------ Here are the changes found in Patchwork_18514 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_flink_basic@flink-lifetime: - fi-tgl-y: [PASS][3] -> [DMESG-WARN][4] ([i915#402]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-tgl-y/igt@gem_flink_basic@flink-lifetime.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-tgl-y/igt@gem_flink_basic@flink-lifetime.html * igt@kms_busy@basic@flip: - fi-kbl-x1275: [PASS][5] -> [DMESG-WARN][6] ([i915#62] / [i915#92] / [i915#95]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-kbl-x1275/igt@kms_busy@basic@flip.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-kbl-x1275/igt@kms_busy@basic@flip.html * igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1: - fi-icl-u2: [PASS][7] -> [DMESG-WARN][8] ([i915#1982]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@b-edp1.html * igt@vgem_basic@unload: - fi-kbl-x1275: [PASS][9] -> [DMESG-WARN][10] ([i915#62] / [i915#92]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-kbl-x1275/igt@vgem_basic@unload.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-kbl-x1275/igt@vgem_basic@unload.html #### Possible fixes #### * {igt@core_hotunplug@unbind-rebind}: - fi-kbl-x1275: [DMESG-WARN][11] ([i915#62] / [i915#92] / [i915#95]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-kbl-x1275/igt@core_hotunplug@unbind-rebind.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-kbl-x1275/igt@core_hotunplug@unbind-rebind.html * igt@gem_tiled_fence_blits@basic: - fi-tgl-y: [DMESG-WARN][13] ([i915#402]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-tgl-y/igt@gem_tiled_fence_blits@basic.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-tgl-y/igt@gem_tiled_fence_blits@basic.html * igt@i915_module_load@reload: - {fi-tgl-dsi}: [DMESG-WARN][15] ([i915#1982] / [k.org#205379]) -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-tgl-dsi/igt@i915_module_load@reload.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-tgl-dsi/igt@i915_module_load@reload.html - fi-byt-j1900: [DMESG-WARN][17] ([i915#1982]) -> [PASS][18] +2 similar issues [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-byt-j1900/igt@i915_module_load@reload.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-byt-j1900/igt@i915_module_load@reload.html - fi-apl-guc: [DMESG-WARN][19] ([i915#1635] / [i915#1982]) -> [PASS][20] +1 similar issue [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-apl-guc/igt@i915_module_load@reload.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-apl-guc/igt@i915_module_load@reload.html - fi-tgl-y: [DMESG-WARN][21] ([i915#1982] / [k.org#205379]) -> [PASS][22] [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-tgl-y/igt@i915_module_load@reload.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-tgl-y/igt@i915_module_load@reload.html * igt@kms_busy@basic@modeset: - fi-tgl-y: [DMESG-WARN][23] ([i915#1982]) -> [PASS][24] +2 similar issues [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-tgl-y/igt@kms_busy@basic@modeset.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-tgl-y/igt@kms_busy@basic@modeset.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic: - {fi-kbl-7560u}: [DMESG-WARN][25] ([i915#1982]) -> [PASS][26] [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-kbl-7560u/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-kbl-7560u/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html - {fi-tgl-dsi}: [DMESG-WARN][27] ([i915#1982]) -> [PASS][28] [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-tgl-dsi/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-tgl-dsi/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html * igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1: - fi-icl-u2: [DMESG-WARN][29] ([i915#1982]) -> [PASS][30] [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-icl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1.html #### Warnings #### * igt@i915_pm_rpm@module-reload: - fi-tgl-y: [DMESG-WARN][31] ([i915#2411]) -> [DMESG-WARN][32] ([i915#1982] / [i915#2411]) [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-tgl-y/igt@i915_pm_rpm@module-reload.html [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-tgl-y/igt@i915_pm_rpm@module-reload.html * igt@kms_force_connector_basic@force-edid: - fi-kbl-x1275: [DMESG-WARN][33] ([i915#62] / [i915#92]) -> [DMESG-WARN][34] ([i915#62] / [i915#92] / [i915#95]) +5 similar issues [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-kbl-x1275/igt@kms_force_connector_basic@force-edid.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-kbl-x1275/igt@kms_force_connector_basic@force-edid.html * igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c: - fi-kbl-x1275: [DMESG-WARN][35] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][36] ([i915#62] / [i915#92]) +2 similar issues [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9019/fi-kbl-x1275/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c.html [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/fi-kbl-x1275/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-c.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635 [i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982 [i915#2373]: https://gitlab.freedesktop.org/drm/intel/issues/2373 [i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411 [i915#289]: https://gitlab.freedesktop.org/drm/intel/issues/289 [i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402 [i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62 [i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92 [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95 [k.org#205379]: https://bugzilla.kernel.org/show_bug.cgi?id=205379 Participating hosts (45 -> 39) ------------------------------ Additional (1): fi-skl-6700k2 Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus Build changes ------------- * Linux: CI_DRM_9019 -> Patchwork_18514 CI-20190529: 20190529 CI_DRM_9019: 038c228475ce10a6f9cc4052250a1315f3c7c627 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5786: 222051026b978ebbc0dc58db62d7a1f29728f95f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_18514: 6d3530687185a0c92e174f706ee93668ce6effe4 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 6d3530687185 drm/i915/dsi: Initiate fame request in cmd mode 3dc23ea7e723 drm/i915/dsi: Add TE handler for dsi cmd mode. 2eaf72b74dd6 i915/dsi: Configure TE interrupt for cmd mode 3aa11f7bf20c drm/i915/dsi: Add details about TE in get_config == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_18514/index.html [-- Attachment #1.2: Type: text/html, Size: 11972 bytes --] [-- Attachment #2: Type: text/plain, Size: 160 bytes --] _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2020-09-17 13:01 UTC | newest] Thread overview: 10+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2020-09-16 16:15 [Intel-gfx] [V12 0/4] Add support for mipi dsi cmd mode Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 1/4] drm/i915/dsi: Add details about TE in get_config Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 2/4] i915/dsi: Configure TE interrupt for cmd mode Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 3/4] drm/i915/dsi: Add TE handler for dsi " Vandita Kulkarni 2020-09-16 16:15 ` [Intel-gfx] [V12 4/4] drm/i915/dsi: Initiate fame request in " Vandita Kulkarni 2020-09-17 11:31 ` Ville Syrjälä 2020-09-17 11:56 ` Kulkarni, Vandita 2020-09-17 12:37 ` Ville Syrjälä 2020-09-17 13:01 ` Kulkarni, Vandita 2020-09-16 17:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Add support for mipi dsi cmd mode (rev12) Patchwork
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox