linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Brian Starkey <Brian.Starkey@arm.com>
Cc: "Julien Yin (Arm Technology China)" <Julien.Yin@arm.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>,
	nd <nd@arm.com>
Subject: [PATCH v2 0/2] Adds slave pipeline support
Date: Tue, 11 Jun 2019 11:13:33 +0000	[thread overview]
Message-ID: <1560251589-31827-1-git-send-email-lowry.li@arm.com> (raw)

Hi,

This serie aims at adding the support for slave pipeline on Komeda
driver. Also adds drop_master to shutdown the device and make sure
all the komeda resources shared between crtcs have been released.

Change since v1:
Rebases the code and resolves the conflict.

This patch series depends on:
- https://patchwork.freedesktop.org/series/60856/

Regards,
Lowry

Lowry Li (Arm Technology China) (2):
  drm/komeda: Add slave pipeline support
  drm/komeda: Adds komeda_kms_drop_master

 drivers/gpu/drm/arm/display/komeda/komeda_crtc.c   | 41 ++++++++++++++++++++--
 drivers/gpu/drm/arm/display/komeda/komeda_kms.c    | 23 ++++++++++++
 drivers/gpu/drm/arm/display/komeda/komeda_kms.h    |  9 +++++
 .../gpu/drm/arm/display/komeda/komeda_pipeline.c   | 22 ++++++++++++
 .../gpu/drm/arm/display/komeda/komeda_pipeline.h   |  2 ++
 .../drm/arm/display/komeda/komeda_pipeline_state.c | 15 ++++++++
 drivers/gpu/drm/arm/display/komeda/komeda_plane.c  | 32 ++++++++++++++++-
 7 files changed, 141 insertions(+), 3 deletions(-)

-- 
1.9.1


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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 11:13 Lowry Li (Arm Technology China) [this message]
2019-06-11 11:13 ` [PATCH v2 1/2] drm/komeda: Add slave pipeline support Lowry Li (Arm Technology China)
2019-06-12 10:51   ` [v2,1/2] " james qian wang (Arm Technology China)
2019-06-11 11:13 ` [PATCH v2 2/2] drm/komeda: Adds komeda_kms_drop_master Lowry Li (Arm Technology China)
2019-06-11 12:30   ` Daniel Vetter
2019-06-12  2:26     ` james qian wang (Arm Technology China)
2019-06-13  8:17       ` Daniel Vetter
2019-06-13  8:28         ` Liviu Dudau
2019-06-13  9:08           ` Daniel Vetter
2019-06-13 13:24             ` Liviu Dudau
2019-06-13 14:30               ` Daniel Vetter
2019-06-14  5:46                 ` james qian wang (Arm Technology China)
2019-06-14  7:01                   ` Daniel Vetter
2019-06-14  8:53                     ` 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=1560251589-31827-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=dri-devel@lists.freedesktop.org \
    --cc=james.qian.wang@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=nd@arm.com \
    --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).