From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 06/19] drm/i915: Add intel_pipe_wm and prepare for watermark pre-compute
Date: Mon, 16 Sep 2013 22:36:02 +0200 [thread overview]
Message-ID: <20130916203601.GD32145@phenom.ffwll.local> (raw)
In-Reply-To: <20130916162914.GK4531@intel.com>
On Mon, Sep 16, 2013 at 07:29:14PM +0300, Ville Syrjälä wrote:
> On Mon, Sep 16, 2013 at 12:07:32PM -0300, Paulo Zanoni wrote:
> > 2013/8/30 <ville.syrjala@linux.intel.com>:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > Introduce a new struct intel_pipe_wm which contains all the
> > > watermarks for a single pipe. Use it to unify the LP0 and LP1+
> > > watermark computations so that we can just iterate through the
> > > watermark levels neatly and call ilk_compute_wm_level() for each.
> > >
> > > Also add another tool ilk_wm_merge() that merges the LP1+ watermarks
> > > from all pipes. For that, embed one intel_pipe_wm inside intel_crtc that
> > > contains the currently valid watermarks for each pipe.
> > >
> > > This is mainly preparatory work for pre-computing the watermarks for
> > > each pipe and merging them at a later time. For now the merging still
> > > happens immediately.
> >
> > >From the commit message, it seems this patch could be split in 4 or 5
> > sub-patches.
>
> I think if I split it up any more then then the indiviual patches might
> stop making sense. Then you're going to be asking "why are you doing this
> change here?" and I have to answer "see patch n+2" or something.
Yeah, I think the patch is ok. It mixes in a few steps, but when
introducing new concepts I think smashing a few really simple things into
the first patch (if the patch is still pretty small like this one here)
helps the reader to understand how it fits together. Then with that
baseline more complex stuff can be converted over ...
Just my 2 uninformed cents ;-)
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-09-16 20:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 11:30 [PATCH 00/19] drm/i915: More HSW watermark prep work ville.syrjala
2013-08-30 11:30 ` [PATCH 01/19] drm/i915: Pass crtc to intel_update_watermarks() ville.syrjala
2013-08-30 20:09 ` Paulo Zanoni
2013-08-30 20:29 ` Ville Syrjälä
2013-09-10 8:40 ` [PATCH v2] " ville.syrjala
2013-08-30 11:30 ` [PATCH 02/19] drm/i915: Call intel_update_watermarks() in specific place during modeset ville.syrjala
2013-08-30 20:26 ` Paulo Zanoni
2013-08-30 20:49 ` Ville Syrjälä
2013-09-02 6:17 ` Daniel Vetter
2013-09-10 8:39 ` [PATCH v2] " ville.syrjala
2013-08-30 11:30 ` [PATCH 03/19] drm/i915: Constify some watermark data ville.syrjala
2013-08-30 20:36 ` Paulo Zanoni
2013-08-30 11:30 ` [PATCH 04/19] drm/i915: Use ilk_compute_wm_level to compute WM_PIPE values ville.syrjala
2013-08-30 21:39 ` Paulo Zanoni
2013-08-30 11:30 ` [PATCH 05/19] drm/i915: Refactor max WM level ville.syrjala
2013-08-30 21:40 ` Paulo Zanoni
2013-09-10 9:17 ` Daniel Vetter
2013-08-30 11:30 ` [PATCH 06/19] drm/i915: Add intel_pipe_wm and prepare for watermark pre-compute ville.syrjala
2013-09-16 15:07 ` Paulo Zanoni
2013-09-16 16:29 ` Ville Syrjälä
2013-09-16 20:36 ` Daniel Vetter [this message]
2013-08-30 11:30 ` [PATCH 07/19] drm/i915: Don't re-compute pipe watermarks except for the affected pipe ville.syrjala
2013-08-30 11:30 ` [PATCH 08/19] drm/i915: Move LP1+ watermark merging out from hsw_compute_wm_results() ville.syrjala
2013-08-30 11:30 ` [PATCH 09/19] drm/i915: Use intel_pipe_wm in hsw_find_best_results ville.syrjala
2013-08-30 11:30 ` [PATCH 10/19] drm/i915: Move some computations out from hsw_compute_wm_parameters() ville.syrjala
2013-08-30 11:30 ` [PATCH 11/19] drm/i915: Don't compute 5/6 DDB split w/ zero active pipes ville.syrjala
2013-08-30 11:30 ` [PATCH 12/19] drm/i915: Refactor wm_lp to level calculation ville.syrjala
2013-08-30 11:30 ` [PATCH 13/19] drm/i915: Kill fbc_wm_enabled from intel_wm_config ville.syrjala
2013-08-30 11:30 ` [PATCH 14/19] drm/i915: Store current watermark state in dev_priv->wm ville.syrjala
2013-08-30 11:30 ` [PATCH 15/19] drm/i915: Improve watermark dirtyness checks ville.syrjala
2013-08-30 11:30 ` [PATCH 16/19] drm/i915: Init HSW watermark tracking in intel_modeset_setup_hw_state() ville.syrjala
2013-08-30 11:30 ` [PATCH 17/19] drm/i915: Remove a somewhat silly debug print from watermark code ville.syrjala
2013-08-30 11:30 ` [PATCH 18/19] drm/i915: Adjust watermark register masks ville.syrjala
2013-08-30 11:30 ` [PATCH 19/19] drm/i915: Add watermark tracepoints ville.syrjala
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=20130916203601.GD32145@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox