All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 08/10] lib/kms: Introduce igt_output_set_crtc()
Date: Wed, 10 Dec 2025 16:48:20 +0200	[thread overview]
Message-ID: <aTmINMHnnFEQbwXH@intel.com> (raw)
In-Reply-To: <f0e5716d96404aa75e67fe200a7c0e9804dd6d39@intel.com>

On Wed, Dec 10, 2025 at 04:38:38PM +0200, Jani Nikula wrote:
> On Wed, 10 Dec 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> > On Wed, 10 Dec 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> >> On Wed, 10 Dec 2025, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> >>> +/**
> >>> + * igt_output_set_pipe:
> >>> + * @output: Target output for which the pipe is being set to
> >>> + * @pipe_obj: Display pipe to set to
> >>> + *
> >>> + * This function sets a @pipe to a specific @output connector by
> >>> + * setting the CRTC_ID property of the @pipe. The pipe
> >>> + * is only activated for all pipes except PIPE_NONE.
> >>> + */
> >>> +void igt_output_set_pipe(igt_output_t *output, enum pipe pipe)
> >>> +{
> >>> +	igt_output_set_crtc(output, igt_crtc_for_pipe(output->display, pipe));
> >>
> >> How does that work for the igt_output_set_pipe(output, PIPE_NONE) calls?
> >> Seems like the idea was to pass NULL here? Or should igt_crtc_for_pipe()
> >> handle PIPE_NONE and return NULL?
> >
> > Okay, so it's just this one commit that's busted, as the whole function
> > is removed in the next patch.
> 
> I think igt_crtc_for_pipe() should handle PIPE_NONE, as there are a
> bunch of places in the next patch that pass, say, data->pipe_id to it,
> and it's a nightmare to check where all those come from.

Ack. I thought I did that already, but apparently not.

> 
> >
> >>
> >>> +}
> >>> +
> >>>  static
> >>>  bool __override_all_active_output_modes_to_fit_bw(igt_display_t *display,
> >>>  						  igt_output_t *outputs[IGT_MAX_PIPES],
> >>> diff --git a/lib/igt_kms.h b/lib/igt_kms.h
> >>> index a9d2d9027ae8..9ec0f08ada24 100644
> >>> --- a/lib/igt_kms.h
> >>> +++ b/lib/igt_kms.h
> >>> @@ -589,6 +589,7 @@ drmModeModeInfo *igt_output_get_highres_mode(igt_output_t *output);
> >>>  drmModeModeInfo *igt_output_get_lowres_mode(igt_output_t *output);
> >>>  void igt_output_override_mode(igt_output_t *output, const drmModeModeInfo *mode);
> >>>  int igt_output_preferred_vrefresh(igt_output_t *output);
> >>> +void igt_output_set_crtc(igt_output_t *output, igt_pipe_t *pipe_obj);
> >>>  void igt_output_set_pipe(igt_output_t *output, enum pipe pipe);
> >>>  igt_plane_t *igt_output_get_plane(igt_output_t *output, int plane_idx);
> >>>  igt_plane_t *igt_output_get_plane_type(igt_output_t *output, int plane_type);
> 
> -- 
> Jani Nikula, Intel

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2025-12-10 14:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10  9:38 [PATCH i-g-t 00/10] lib/kms: Move towards using 'crtcs' instead of 'pipes' Ville Syrjala
2025-12-10  9:38 ` [PATCH i-g-t 01/10] tests/intel/kms_dp_linktrain_fallback: Reduce side effects in igt_output_set_pipe() args Ville Syrjala
2025-12-10 14:21   ` Jani Nikula
2025-12-10  9:38 ` [PATCH i-g-t 02/10] lib/kms: Introduce igt_display_n_crtcs() Ville Syrjala
2025-12-10 14:21   ` Jani Nikula
2025-12-10  9:38 ` [PATCH i-g-t 03/10] lib/kms: Use igt_display_n_crtcs() everywhere Ville Syrjala
2025-12-10 14:22   ` Jani Nikula
2025-12-10  9:38 ` [PATCH i-g-t 04/10] lib/kms: Introduce igt_crtc_for_pipe() Ville Syrjala
2025-12-10 14:23   ` Jani Nikula
2025-12-10 17:16   ` [PATCH i-g-t v2 " Ville Syrjala
2025-12-10  9:38 ` [PATCH i-g-t 05/10] lib/kms: Use igt_crtc_for_pipe() everywhere Ville Syrjala
2025-12-10 14:25   ` Jani Nikula
2025-12-12 15:32     ` Ville Syrjälä
2025-12-10  9:38 ` [PATCH i-g-t 06/10] lib/kms: Remove tall tales about 'pipe' in DRM_IOCTL_WAIT_VBLANK Ville Syrjala
2025-12-10 14:25   ` Jani Nikula
2025-12-10  9:39 ` [PATCH i-g-t 07/10] lib/kms: Pass the entire igt_pipe_t to igt_wait_for_vblank*() Ville Syrjala
2025-12-10 14:29   ` Jani Nikula
2025-12-10  9:39 ` [PATCH i-g-t 08/10] lib/kms: Introduce igt_output_set_crtc() Ville Syrjala
2025-12-10 14:34   ` Jani Nikula
2025-12-10 14:36     ` Jani Nikula
2025-12-10 14:38       ` Jani Nikula
2025-12-10 14:44         ` Jani Nikula
2025-12-10 14:48         ` Ville Syrjälä [this message]
2025-12-10  9:39 ` [PATCH i-g-t 09/10] lib/kms: Replace igt_output_set_pipe() with igt_output_set_crtc() Ville Syrjala
2025-12-10 14:42   ` Jani Nikula
2025-12-10  9:39 ` [PATCH i-g-t 10/10] lib/kms: Rename igt_pipe_t to igt_crtc_t Ville Syrjala
2025-12-10 14:43   ` Jani Nikula
2025-12-10 13:34 ` ✓ Xe.CI.BAT: success for lib/kms: Move towards using 'crtcs' instead of 'pipes' Patchwork
2025-12-10 14:12 ` ✗ i915.CI.BAT: failure " Patchwork
2025-12-10 19:49 ` ✗ Xe.CI.Full: " 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=aTmINMHnnFEQbwXH@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jani.nikula@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.