From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 61030EC8 for ; Thu, 9 Nov 2023 17:25:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="J2iuSO0l" Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BD5D53841 for ; Thu, 9 Nov 2023 09:25:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1699550720; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LQsLMrBO0s8gsbhcurrkAKTlTUKc8bmHZW0Ex5lVbpk=; b=J2iuSO0lShKtr7Yfs0J9RRhcGgBnWWT6Torza87BqDgxi97QwUDF6YUndjdEgflLpDA3R8 dgFP0O7MRQBwq/TwBp+oNFOgWqo6jTTPLiCTAOC0GEpALlo6XX0HedEoIHcHRDpyHd7xBu OkWx3GF8qAinj6BBu/e9reC3F91fPBE= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-213-KzrdexzjNWurIGTvN8OHYQ-1; Thu, 09 Nov 2023 12:25:19 -0500 X-MC-Unique: KzrdexzjNWurIGTvN8OHYQ-1 Received: by mail-wr1-f70.google.com with SMTP id ffacd0b85a97d-32f7cfab43eso568376f8f.1 for ; Thu, 09 Nov 2023 09:25:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699550718; x=1700155518; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=LQsLMrBO0s8gsbhcurrkAKTlTUKc8bmHZW0Ex5lVbpk=; b=Na7NnUsc1lsF4xzfjegYq62oZKeRxqGqE2zfVruQTiodlls7DHzDUevMHqcVO92/qS IZbuEbTi/3IzznUm8HI+ZJRFkNXd5osAh/OxUwbs7/4fQMgNl+CRg/pkqXry1doQe5QC cZUENfhG7UaNwoCTuVen8sM36XM9dncTB2y4M7wvytlyyBf5mBiJ16IuLCdMMkBySxA8 KOD5XJp6x+tbSQj+y1VA48FzZZ046veiXQa2cenJx6kLauK8tzdFgNYey24IvGvUMKuI gWi0KlDSFakbedTVJeoNHhWwd6e0cyf46svKTRzAYdVZlB5nZChUGKw8V9mJcRvuaATw eHJg== X-Gm-Message-State: AOJu0Ywkn7yYbeNsNiyPZ/rer7FKo60hKSYg2+QFE28NdzPaiu+B7MCy oJVgULSRDE7uETWMfYnHGRSPtGheQmAAUediUp4oNUeXFfvktis9qKmmf2CM8Gi0JWYypwCRnWn wlthJ1CYVVMFc9BUvojMX X-Received: by 2002:a05:6000:1cb:b0:32f:7963:8493 with SMTP id t11-20020a05600001cb00b0032f79638493mr4461557wrx.37.1699550718114; Thu, 09 Nov 2023 09:25:18 -0800 (PST) X-Google-Smtp-Source: AGHT+IGD/Ij413ZeKujXk6kJlWHHEPZiWIxqmSIPmvd4/ZL4FLHzk3PoQZkslp1/W1fbI9IJfywcfQ== X-Received: by 2002:a05:6000:1cb:b0:32f:7963:8493 with SMTP id t11-20020a05600001cb00b0032f79638493mr4461536wrx.37.1699550717778; Thu, 09 Nov 2023 09:25:17 -0800 (PST) Received: from localhost (205.pool92-176-231.dynamic.orange.es. [92.176.231.205]) by smtp.gmail.com with ESMTPSA id k8-20020a5d6e88000000b0032db430fb9bsm121425wrz.68.2023.11.09.09.25.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 09 Nov 2023 09:25:17 -0800 (PST) From: Javier Martinez Canillas To: linux-kernel@vger.kernel.org Cc: Simon Ser , Sima Vetter , Pekka Paalanen , Maxime Ripard , Bilal Elmoussaoui , Erico Nunes , Javier Martinez Canillas , Daniel Vetter , David Airlie , Jonathan Corbet , Maarten Lankhorst , Thomas Zimmermann , dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org Subject: [PATCH 6/6] drm/todo: Add entry about implementing buffer age for damage tracking Date: Thu, 9 Nov 2023 18:24:40 +0100 Message-ID: <20231109172449.1599262-7-javierm@redhat.com> X-Mailer: git-send-email 2.41.0 In-Reply-To: <20231109172449.1599262-1-javierm@redhat.com> References: <20231109172449.1599262-1-javierm@redhat.com> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Currently, only damage tracking for frame damage is supported. If a driver needs to do buffer damage (e.g: the framebuffer attached to plane's state has changed since the last page-flip), the damage helpers just fallback to a full plane update. Add en entry in the TODO about implementing buffer age or any other damage accumulation algorithm for buffer damage handling. Suggested-by: Simon Ser Signed-off-by: Javier Martinez Canillas --- Documentation/gpu/todo.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst index 03fe5d1247be..adaa154210a0 100644 --- a/Documentation/gpu/todo.rst +++ b/Documentation/gpu/todo.rst @@ -765,6 +765,26 @@ Contact: Hans de Goede Level: Advanced +Buffer age or other damage accumulation algorithm for buffer damage handling +============================================================================ + +Drivers that do per-buffer uploads, need a buffer damage handling (rather than +frame damage like drivers that do per-plane or per-CRTC uploads), but there is +no support to get the buffer age or any other damage accumulation algorithm. + +For this reason, the damage helpers just fallback to a full plane update if the +framebuffer attached to a plane has changed since the last page-flip. + +This should be improved to get damage tracking properly working on drivers that +do per-buffer uploads. + +More information about damage tracking and references to learning materials in +`Damage Tracking Properties `_ + +Contact: Javier Martinez Canillas + +Level: Advanced + Outside DRM =========== -- 2.41.0