linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Noralf Trønnes" <noralf@tronnes.org>,
	daniel@ffwll.ch, airlied@linux.ie, mripard@kernel.org,
	maarten.lankhorst@linux.intel.com, drawat.floss@gmail.com,
	airlied@redhat.com, kraxel@redhat.com, david@lechnology.com,
	sam@ravnborg.org, javierm@redhat.com, kernel@amanoeldawod.com,
	dirty.ice.hu@gmail.com, michael+lkml@stapelberg.ch, aros@gmx.com,
	joshua@stroblindustries.com, arnd@arndb.de
Cc: linux-hyperv@vger.kernel.org, dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v3 7/9] drm/simpledrm: Enable FB_DAMAGE_CLIPS property
Date: Wed, 10 Nov 2021 13:48:00 +0100	[thread overview]
Message-ID: <19ba897d-9007-a103-581e-060c5ce1c9ed@suse.de> (raw)
In-Reply-To: <0e762e67-b18f-3cbd-b401-d6766a7168a3@tronnes.org>


[-- Attachment #1.1: Type: text/plain, Size: 1041 bytes --]

Hi

Am 10.11.21 um 13:34 schrieb Noralf Trønnes:
> 
> 
> Den 10.11.2021 11.37, skrev Thomas Zimmermann:
>> Enable the FB_DAMAGE_CLIPS property to reduce display-update
>> overhead. Also fixes a warning in the kernel log.
>>
>>    simple-framebuffer simple-framebuffer.0: [drm] drm_plane_enable_fb_damage_clips() not called
>>
>> Fix the computation of the blit rectangle. This wasn't an issue so
>> far, as simpledrm always blitted the full framebuffer. The code now
>> supports damage clipping and virtual screen sizes.
>>
>> v3:
>> 	* fix drm_dev_enter() error path (Noralf)
>> 	* remove unnecessary clipping from update function (Noralf)
>>
>> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
>> ---
> 
> Reviewed-by: Noralf Trønnes <noralf@tronnes.org>
> 

Thank you so much for reviewing.

Best regards
Thomas

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Ivo Totev

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2021-11-10 12:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 10:36 [PATCH v3 0/9] drm/simpledrm: Enable damage clips and virtual screens Thomas Zimmermann
2021-11-10 10:36 ` [PATCH v3 1/9] drm/format-helper: Export drm_fb_clip_offset() Thomas Zimmermann
2021-11-10 10:36 ` [PATCH v3 2/9] drm/format-helper: Rework format-helper memcpy functions Thomas Zimmermann
2021-11-10 10:36 ` [PATCH v3 3/9] drm/format-helper: Add destination-buffer pitch to drm_fb_swab() Thomas Zimmermann
2021-11-10 10:36 ` [PATCH v3 4/9] drm/format-helper: Rework format-helper conversion functions Thomas Zimmermann
2021-11-10 10:36 ` [PATCH v3 5/9] drm/format-helper: Streamline blit-helper interface Thomas Zimmermann
2021-11-10 10:36 ` [PATCH v3 6/9] drm/fb-helper: Allocate shadow buffer of surface height Thomas Zimmermann
2021-11-10 10:37 ` [PATCH v3 7/9] drm/simpledrm: Enable FB_DAMAGE_CLIPS property Thomas Zimmermann
2021-11-10 12:34   ` Noralf Trønnes
2021-11-10 12:48     ` Thomas Zimmermann [this message]
2021-11-10 10:37 ` [PATCH v3 8/9] drm/simpledrm: Support virtual screen sizes Thomas Zimmermann
2021-11-10 10:37 ` [PATCH v3 9/9] drm: Clarify semantics of struct drm_mode_config.{min,max}_{width,height} Thomas Zimmermann

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=19ba897d-9007-a103-581e-060c5ce1c9ed@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=arnd@arndb.de \
    --cc=aros@gmx.com \
    --cc=daniel@ffwll.ch \
    --cc=david@lechnology.com \
    --cc=dirty.ice.hu@gmail.com \
    --cc=drawat.floss@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=joshua@stroblindustries.com \
    --cc=kernel@amanoeldawod.com \
    --cc=kraxel@redhat.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=michael+lkml@stapelberg.ch \
    --cc=mripard@kernel.org \
    --cc=noralf@tronnes.org \
    --cc=sam@ravnborg.org \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).