public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Simona Vetter <simona.vetter@ffwll.ch>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: "Imre Deak" <imre.deak@intel.com>,
	"Jouni Högander" <jouni.hogander@intel.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>
Subject: linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree
Date: Tue, 10 Mar 2026 13:34:55 +0000	[thread overview]
Message-ID: <abAd_71qonm8fvk7@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 2388 bytes --]

Hi all,

Today's linux-next merge of the drm-intel tree got a conflict in:

  drivers/gpu/drm/i915/display/intel_vdsc.h

between commit:

  bb5f1cd10101c ("drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters")

from the drm-intel-fixes tree and commits:

  c8698d61aeb3f ("drm/i915/dsc: Add helper for writing DSC Selective Update ET parameters")
  91f0a94974144 ("drm/i915/dsc: Add intel_dsc_get_slice_config()")
  889ff8dd4679a ("drm/i915/dsc: Track the detaild DSC slice configuration")

from the drm-intel tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --combined drivers/gpu/drm/i915/display/intel_vdsc.h
index 99bb9042592a4,3372f8694054d..0000000000000
--- a/drivers/gpu/drm/i915/display/intel_vdsc.h
+++ b/drivers/gpu/drm/i915/display/intel_vdsc.h
@@@ -13,10 -13,16 +13,16 @@@ struct drm_printer
  enum transcoder;
  struct intel_crtc;
  struct intel_crtc_state;
+ struct intel_display;
  struct intel_dsb;
+ struct intel_dsc_slice_config;
  struct intel_encoder;
  
  bool intel_dsc_source_support(const struct intel_crtc_state *crtc_state);
+ int intel_dsc_line_slice_count(const struct intel_dsc_slice_config *config);
+ bool intel_dsc_get_slice_config(struct intel_display *display,
+ 				int num_joined_pipes, int slice_per_pipe,
+ 				struct intel_dsc_slice_config *config);
  void intel_uncompressed_joiner_enable(const struct intel_crtc_state *crtc_state);
  void intel_dsc_enable(const struct intel_crtc_state *crtc_state);
  void intel_dsc_disable(const struct intel_crtc_state *crtc_state);
@@@ -38,5 -44,8 +44,8 @@@ void intel_vdsc_state_dump(struct drm_p
  			   const struct intel_crtc_state *crtc_state);
  int intel_vdsc_min_cdclk(const struct intel_crtc_state *crtc_state);
  unsigned int intel_vdsc_prefill_lines(const struct intel_crtc_state *crtc_state);
+ int intel_dsc_get_pixel_rate_with_dsc_bubbles(struct intel_display *display,
+ 					      int pixel_rate, int htotal,
+ 					      int dsc_horizontal_slices);
  
  #endif /* __INTEL_VDSC_H__ */

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-03-10 13:35 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 13:34 Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-23 16:10 linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree Mark Brown
2025-10-16 13:56 Mark Brown
2025-10-14 12:29 Mark Brown
2024-12-03 20:05 Mark Brown
2019-03-21 23:57 Stephen Rothwell
2019-03-31 22:59 ` Stephen Rothwell
2017-10-18  9:27 Mark Brown
2017-10-16 11:35 Mark Brown
2017-10-17  8:11 ` Arnd Bergmann
2017-10-17  8:30   ` Mark Brown
2017-10-12 18:44 Mark Brown
2017-10-12 18:36 Mark Brown
2017-06-08  3:07 Stephen Rothwell
2017-06-08  3:04 Stephen Rothwell
2017-03-21  0:37 Stephen Rothwell
2016-08-24  1:42 Stephen Rothwell
2016-08-24  1:32 Stephen Rothwell
2016-06-22  1:40 Stephen Rothwell
2015-11-18  0:30 Stephen Rothwell
2015-09-30  1:32 Stephen Rothwell
2015-09-24  1:25 Stephen Rothwell
2015-09-24  8:57 ` Jani Nikula
2015-09-24 11:52   ` Stephen Rothwell
2015-07-15  0:15 Stephen Rothwell
2015-07-14  2:11 Stephen Rothwell
2015-07-14  7:34 ` Daniel Vetter
2015-07-10  2:15 Stephen Rothwell
2015-07-10  2:08 Stephen Rothwell
2015-02-27  0:36 Stephen Rothwell
2015-02-26  0:15 Stephen Rothwell
2015-02-25  1:05 Stephen Rothwell
2015-01-09  2:06 Stephen Rothwell
2014-05-22  5:58 Stephen Rothwell
2014-04-30  2:37 Stephen Rothwell
2013-12-16  1:45 Stephen Rothwell
2013-12-02  1:04 Stephen Rothwell
2013-12-02  1:13 ` Stephen Rothwell
2013-09-25  2:00 Stephen Rothwell
2013-09-20  1:40 Stephen Rothwell
2013-07-26  3:14 Stephen Rothwell
2013-07-26  3:10 Stephen Rothwell
2013-07-18  2:07 Stephen Rothwell
2013-07-18  1:44 Stephen Rothwell
2013-07-16  2:05 Stephen Rothwell

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=abAd_71qonm8fvk7@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=jouni.hogander@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona.vetter@ffwll.ch \
    --cc=tursulin@ursulin.net \
    /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