From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Navare, Manasi" <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display/: Refactor hsw_crtc_enable for bigjoiner cleanup
Date: Wed, 30 Mar 2022 12:53:22 +0300 [thread overview]
Message-ID: <YkQokpy3cuXgXjnf@intel.com> (raw)
In-Reply-To: <20220330000034.GA30948@labuser-Z97X-UD5H>
On Tue, Mar 29, 2022 at 05:00:39PM -0700, Navare, Manasi wrote:
> Hi Ville,
>
> I was looking at your suggestion of extracting the per pipe stuff out.
> Currently in hsw_crtc_enable: the Only non per pipe stuff which gets enabled for the encoders is :
> encoder specific is pre_pll_enable(), enable_shared_dpll, encoders_pre_enable and configure_cpu_transcoder() - All of this
> can be put in a function hsw_encoder_configure() or something that can still be called from with hsw_crtc_enable
I don't see a need to move that stuff anywhere. Just leave it
in hsw_crtc_enable() IMO.
>
> Then the remaining can go into a per pipe function that can be called for each slave pipe
This is what I have been suggesting.
But I think there's also some per-pipe stuff currently in the
the encoder hooks, and some of that is only done for the master
there whereaas the slave part I think are somewhere else. We
should attempt to fix that as well so that every step is done
in a consistent manner for every pipe be it master or slave.
--
Ville Syrjälä
Intel
prev parent reply other threads:[~2022-03-30 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 23:38 [Intel-gfx] [PATCH] drm/i915/display/: Refactor hsw_crtc_enable for bigjoiner cleanup Manasi Navare
2022-03-16 0:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-03-16 3:21 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-16 7:48 ` [Intel-gfx] [PATCH] " Jani Nikula
2022-03-16 17:10 ` Navare, Manasi
2022-03-17 15:35 ` Jani Nikula
2022-03-17 18:28 ` Navare, Manasi
2022-03-17 18:31 ` Navare, Manasi
2022-03-17 19:15 ` Jani Nikula
2022-03-17 18:52 ` Ville Syrjälä
2022-03-17 19:05 ` Navare, Manasi
2022-03-17 19:14 ` Ville Syrjälä
2022-03-30 0:00 ` Navare, Manasi
2022-03-30 9:53 ` Ville Syrjälä [this message]
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=YkQokpy3cuXgXjnf@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=manasi.d.navare@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.