From: Sasha Levin <sashal@kernel.org>
To: "Sasha Levin" <sashal@kernel.org>,
"Ville Syrjala" <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Stefan Gottwald <gottwald@igel.com>, stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Make sure cdclk is high enough for DP audio on VLV/CHV
Date: Wed, 17 Jul 2019 15:14:03 +0000 [thread overview]
Message-ID: <20190717151404.42A1D2182B@mail.kernel.org> (raw)
In-Reply-To: <20190717114536.22937-1-ville.syrjala@linux.intel.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.2.1, v5.1.18, v4.19.59, v4.14.133, v4.9.185, v4.4.185.
v5.2.1: Failed to apply! Possible dependencies:
Unable to calculate
v5.1.18: Failed to apply! Possible dependencies:
Unable to calculate
v4.19.59: Failed to apply! Possible dependencies:
Unable to calculate
v4.14.133: Failed to apply! Possible dependencies:
9c61de4c69a2 ("drm/i915: Consolidate max_cdclk_freq check in intel_crtc_compute_min_cdclk()")
c8dae55a8ced ("drm/i915/vlv: Add cdclk workaround for DSI")
d305e0614601 ("drm/i915: Track minimum acceptable cdclk instead of "minimum dotclock"")
v4.9.185: Failed to apply! Possible dependencies:
294591cfbd2b ("drm/i915: Update kerneldoc for intel_dpll_mgr.c")
2c42e5351445 ("drm/i915: Rename intel_shared_dpll_config to intel_shared_dpll_state")
3c0fb58820ac ("drm/i915: Rename intel_shared_dpll_commit() to _swap_state()")
47a6bc61b866 ("drm/i915: Move broxton phy code to intel_dpio_phy.c")
7ff89ca21358 ("drm/i915: Move most cdclk/rawclk related code to intel_cdclk.c")
842d416654eb ("drm/i915: Create a struct to hold information about the broxton phys")
8cbeb06dc6b5 ("drm/i915: Implement cdclk restrictions based on Azalia BCLK")
a1c414ee82d9 ("drm/i915: Introduce intel_release_shared_dpll()")
b284eedaf74b ("drm/i915: Pass lane count to bxt_ddi_phy_calc_lane_optmin_mask()")
b6e08203cc1f ("drm/i915: Move broxton vswing sequence to intel_dpio_phy.c")
c8dae55a8ced ("drm/i915/vlv: Add cdclk workaround for DSI")
ed37892e6df2 ("drm/i915: Address broxton phy registers based on phy and channel number")
f38861b814b5 ("drm/i915: Move DPIO phy documentation section to intel_dpio_phy.c")
v4.4.185: Failed to apply! Possible dependencies:
12fda3876d08 ("drm/i915/ibx: Ensure the HW is powered during PLL HW readout")
22cba31bae9d ("Documentation/sphinx: add basic working Sphinx configuration and build")
294591cfbd2b ("drm/i915: Update kerneldoc for intel_dpll_mgr.c")
64e1077a1f93 ("drm/i915: Clean up eDP PLL state asserts")
7abd4b35a577 ("drm/i915: Move shared dpll code to a new file")
7ff89ca21358 ("drm/i915: Move most cdclk/rawclk related code to intel_cdclk.c")
87ad321287ae ("drm/i915: add onoff utility function")
8cbeb06dc6b5 ("drm/i915: Implement cdclk restrictions based on Azalia BCLK")
c8dae55a8ced ("drm/i915/vlv: Add cdclk workaround for DSI")
ca00c2b986ea ("Documentation/gpu: split up the gpu documentation")
cb597fcea5c2 ("Documentation/gpu: add new gpu.rst converted from DocBook gpu.tmpl")
f169660ed4e5 ("drm/i915/dp: Add a standalone function to obtain shared dpll for HSW/BDW/SKL/BXT")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-17 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 11:45 [PATCH] drm/i915: Make sure cdclk is high enough for DP audio on VLV/CHV Ville Syrjala
2019-07-17 12:30 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-07-17 12:49 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-17 15:14 ` Sasha Levin [this message]
2019-07-17 15:59 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-18 17:11 ` [Intel-gfx] [PATCH] " Chris Wilson
2019-07-18 18:04 ` Ville Syrjälä
2019-07-18 18:15 ` Chris Wilson
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=20190717151404.42A1D2182B@mail.kernel.org \
--to=sashal@kernel.org \
--cc=gottwald@igel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--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.