public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 3/4] drm/i915: move more atomic plane declarations to intel_atomic_plane.h
Date: Mon, 10 Jun 2019 11:12:06 +0300	[thread overview]
Message-ID: <87tvcxn9k9.fsf@intel.com> (raw)
In-Reply-To: <155982418768.19464.12709931321184255863@skylake-alporthouse-com>

On Thu, 06 Jun 2019, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2019-06-06 13:22:02)
>> Some function declarations in intel_drv.h were missed when
>> intel_atomic_plane.h was created.
>> 
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/i915/intel_atomic_plane.h | 16 ++++++++++++++++
>>  drivers/gpu/drm/i915/intel_drv.h          | 12 ------------
>>  2 files changed, 16 insertions(+), 12 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/intel_atomic_plane.h b/drivers/gpu/drm/i915/intel_atomic_plane.h
>> index 0a9651376d0e..24320041498d 100644
>> --- a/drivers/gpu/drm/i915/intel_atomic_plane.h
>> +++ b/drivers/gpu/drm/i915/intel_atomic_plane.h
>> @@ -6,7 +6,11 @@
>>  #ifndef __INTEL_ATOMIC_PLANE_H__
>>  #define __INTEL_ATOMIC_PLANE_H__
>>  
>> +#include <linux/types.h>
>> +
>> +struct drm_crtc_state;
>>  struct drm_plane;
>> +struct drm_property;
>>  struct intel_atomic_state;
>>  struct intel_crtc;
>>  struct intel_crtc_state;
>> @@ -38,5 +42,17 @@ int intel_plane_atomic_check_with_state(const struct intel_crtc_state *old_crtc_
>>                                         struct intel_crtc_state *crtc_state,
>>                                         const struct intel_plane_state *old_plane_state,
>>                                         struct intel_plane_state *intel_state);
>> +int intel_plane_atomic_get_property(struct drm_plane *plane,
>> +                                   const struct drm_plane_state *state,
>> +                                   struct drm_property *property,
>> +                                   u64 *val);
>> +int intel_plane_atomic_set_property(struct drm_plane *plane,
>> +                                   struct drm_plane_state *state,
>> +                                   struct drm_property *property,
>> +                                   u64 val);
>> +int intel_plane_atomic_calc_changes(const struct intel_crtc_state *old_crtc_state,
>> +                                   struct drm_crtc_state *crtc_state,
>> +                                   const struct intel_plane_state *old_plane_state,
>> +                                   struct drm_plane_state *plane_state);
>
> intel_plane_atomic vs intel_atomic_plane.h that must be hitting the ocd
> sweetspot.

Right in the nerve indeed. Something for the future.

> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Thanks, pushed the lot.

BR,
Jani.



-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-06-10  8:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 12:22 [PATCH v2 1/4] drm/i915: move pm related declarations to intel_pm.h Jani Nikula
2019-06-06 12:22 ` [PATCH v2 2/4] drm/i915: remove some unused declarations from intel_drv.h Jani Nikula
2019-06-06 12:28   ` Chris Wilson
2019-06-06 12:22 ` [PATCH v2 3/4] drm/i915: move more atomic plane declarations to intel_atomic_plane.h Jani Nikula
2019-06-06 12:29   ` Chris Wilson
2019-06-10  8:12     ` Jani Nikula [this message]
2019-06-06 12:22 ` [PATCH v2 4/4] drm/i915/frontbuffer: remove obsolete comment about mark busy/idle Jani Nikula
2019-06-06 12:30   ` Chris Wilson
2019-06-06 12:28 ` [PATCH v2 1/4] drm/i915: move pm related declarations to intel_pm.h Chris Wilson
2019-06-06 14:05 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/4] " Patchwork
2019-06-08 17:11 ` ✓ Fi.CI.IGT: " 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=87tvcxn9k9.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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