From: "Lowry Li (Arm Technology China)" <Lowry.Li@arm.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>,
"james qian wang (Arm Technology China)"
<james.qian.wang@arm.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"seanpaul@chromium.org" <seanpaul@chromium.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
Brian Starkey <Brian.Starkey@arm.com>
Cc: "Julien Yin (Arm Technology China)" <Julien.Yin@arm.com>,
"maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
"eric@anholt.net" <eric@anholt.net>,
"kieran.bingham+renesas@ideasonboard.com"
<kieran.bingham+renesas@ideasonboard.com>,
"sean@poorly.run" <sean@poorly.run>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"Jonathan Chai (Arm Technology China)" <Jonathan.Chai@arm.com>,
Ayan Halder <Ayan.Halder@arm.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>, nd <nd@arm.com>
Subject: [PATCH v1 0/2] Free the writeback_job when it with an empty fb
Date: Wed, 31 Jul 2019 11:04:30 +0000 [thread overview]
Message-ID: <1564571048-15029-1-git-send-email-lowry.li@arm.com> (raw)
Hi,
This serie aims at adding the check and free the writeback_job when it
with an empty fb in drm_atomic_connector_check().
Also did some refine in drm_writeback_signal_completion() to clear the
fence pointer when writeback job signaled.
This patchset is based at the drm-misc-fixes branch.
Lowry Li (Arm Technology China) (2):
drm: Free the writeback_job when it with an empty fb
drm: Clear the fence pointer when writeback job signaled
.../drm/arm/display/komeda/komeda_wb_connector.c | 3 +--
drivers/gpu/drm/arm/malidp_mw.c | 4 ++--
drivers/gpu/drm/drm_atomic.c | 13 ++++++++----
drivers/gpu/drm/drm_writeback.c | 23 ++++++++++++++--------
drivers/gpu/drm/rcar-du/rcar_du_writeback.c | 4 ++--
drivers/gpu/drm/vc4/vc4_txp.c | 5 ++---
6 files changed, 31 insertions(+), 21 deletions(-)
--
1.9.1
next reply other threads:[~2019-07-31 11:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 11:04 Lowry Li (Arm Technology China) [this message]
2019-07-31 11:04 ` [PATCH v1 1/2] drm: Free the writeback_job when it with an empty fb Lowry Li (Arm Technology China)
2019-07-31 13:03 ` Liviu Dudau
2019-09-23 7:24 ` [v1,1/2] " james qian wang (Arm Technology China)
2019-07-31 11:04 ` [PATCH v1 2/2] drm: Clear the fence pointer when writeback job signaled Lowry Li (Arm Technology China)
2019-07-31 13:15 ` Liviu Dudau
[not found] ` <20190801063055.GA17887@lowry.li@arm.com>
2019-08-01 9:58 ` Liviu Dudau
2019-07-31 13:20 ` Brian Starkey
[not found] ` <20190801063351.GB17887@lowry.li@arm.com>
2019-08-02 9:29 ` Brian Starkey
2019-08-02 9:43 ` Daniel Vetter
2019-08-02 9:45 ` Daniel Vetter
2019-08-02 10:09 ` Brian Starkey
2019-08-02 14:06 ` Daniel Vetter
2019-08-02 10:09 ` james qian wang (Arm Technology China)
2019-08-05 13:10 ` Brian Starkey
2019-09-23 7:25 ` [v1,2/2] " james qian wang (Arm Technology China)
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=1564571048-15029-1-git-send-email-lowry.li@arm.com \
--to=lowry.li@arm.com \
--cc=Ayan.Halder@arm.com \
--cc=Brian.Starkey@arm.com \
--cc=Jonathan.Chai@arm.com \
--cc=Julien.Yin@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=james.qian.wang@arm.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=nd@arm.com \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.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).