From: sonika <sonika.jindal@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] Adding rotattion to drm_plane_helper_check_update
Date: Wed, 14 Jan 2015 09:54:45 +0530 [thread overview]
Message-ID: <54B5EF8D.8060606@intel.com> (raw)
In-Reply-To: <20150113181229.GB8851@intel.com>
On Tuesday 13 January 2015 11:42 PM, Matt Roper wrote:
> On Tue, Jan 13, 2015 at 06:03:38PM +0530, Sonika Jindal wrote:
>> This adds another parameter rotation to drm_plane_helper_check_update.
>> This will enable this function to do to size updations based upon the rotation
>> if any.
>> Updated the calls to this function in i915 and drm. Rockchip driver also needs
>> to be updated.
> It looks like you add the new function parameter in patch 1, but don't
> add it to the i915 callsites until patch 2 (and don't add it to the
> rockchip driver at all in this series). That means that if someone is
> bisecting the kernel and lands on this commit, some of the drivers will
> fail to build, which isn't good.
>
> The callsites need to be updated at the same time that you add the
> parameter; fortunately there are only four of them (two in i915, one in
> the generic plane helper, and one in rockchip). For simplicity, you can
> just pass the DRM_ROTATE_0 bit initially at the updated callsites when
> you add the new parameter so that there's no change from the current
> behavior for the existing callers. Then you can come back in later in
> driver-specific patch(es) and pass the real rotation value the driver is
> using and adjust the caller's functionality as appropriate.
Sure, I will do this.
Sonika
>
> Matt
>
>> Sonika Jindal (2):
>> drm: Adding rotation to drm_plane_helper_check_update
>> drm/i915: Passing rotation to drm_plane_helper_check_update
>>
>> drivers/gpu/drm/drm_plane_helper.c | 79 ++++++++++++++++++++++++++++++++--
>> drivers/gpu/drm/i915/intel_display.c | 6 ++-
>> include/drm/drm_plane_helper.h | 3 +-
>> 3 files changed, 81 insertions(+), 7 deletions(-)
>>
>> --
>> 1.7.10.4
>>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-01-14 4:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 12:33 [PATCH 0/2] Adding rotattion to drm_plane_helper_check_update Sonika Jindal
2015-01-13 12:33 ` [PATCH 1/2] drm: Adding rotation " Sonika Jindal
2015-01-13 13:32 ` [Intel-gfx] " Ville Syrjälä
2015-01-14 4:35 ` sonika
2015-01-14 9:27 ` Ville Syrjälä
2015-01-14 9:35 ` [Intel-gfx] " Jindal, Sonika
2015-01-14 9:49 ` Jindal, Sonika
2015-01-14 11:43 ` Ville Syrjälä
2015-01-14 13:54 ` Jindal, Sonika
2015-01-14 18:08 ` Ville Syrjälä
2015-01-15 2:04 ` [Intel-gfx] " Jindal, Sonika
2015-01-15 9:28 ` Ville Syrjälä
2015-01-14 5:40 ` [PATCH] " Sonika Jindal
2015-01-14 16:32 ` Matt Roper
2015-01-15 10:39 ` shuang.he
2015-01-13 12:33 ` [PATCH 2/2] drm/i915: Passing " Sonika Jindal
2015-01-13 19:36 ` shuang.he
2015-01-13 18:12 ` [PATCH 0/2] Adding rotattion " Matt Roper
2015-01-14 4:24 ` sonika [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=54B5EF8D.8060606@intel.com \
--to=sonika.jindal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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