All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: keith <keith.zhao@starfivetech.com>,
	andrzej.hajda@intel.com, neil.armstrong@linaro.org,
	rfoss@kernel.org, Laurent.pinchart@ideasonboard.com,
	jonas@kwiboo.se, jernej.skrabec@gmail.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	hjc@rock-chips.com, heiko@sntech.de, andy.yan@rock-chips.com,
	xingyu.wu@starfivetech.com, p.zabel@pengutronix.de,
	jack.zhu@starfivetech.com, shengyang.chen@starfivetech.com
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 00/10] drm/verisilicon : support DC8200 and inno hdmi
Date: Tue, 21 May 2024 09:18:49 +0200	[thread overview]
Message-ID: <9949da52-c7ec-4a95-b323-8e40ef4af06e@kernel.org> (raw)
In-Reply-To: <20240521105817.3301-1-keith.zhao@starfivetech.com>

On 21/05/2024 12:58, keith wrote:
> Verisilicon/DC8200 display controller IP has 2 display pipes and each 
> pipe support a primary plane and a cursor plane . 
> In addition, there are four overlay planes as two display pipes common resources.
> 
> The first display pipe is bound to the inno HDMI encoder.
> The second display pipe is bound to a simple encoder, which is used to
> find dsi bridge by dts node. 
> 
> Patch 1 adds YAML schema for JH7110 display pipeline.
> 
> Patches 2 to 3 add inno common api and match the ROCKCHIP inno hdmi driver 
> by calling the common api. 
> The collating public interface is based on ROCKCHIP inno hdmi, 
> and it can be resused by JH7110 inno hdmi.
> Those common api are tested on rk-3128 SDK, which kernel version is 4.x. 
> step1, make sure the process is consistent with the latest kernel version.
> step2, just remove the interface and add a common interface. 
> 
> Patches 4 to 8 add kms driver for dc8200 display controller.
> 
> Patch 9 adds inno hdmi support for JH7110 display pipeline.
> 
> Patch 10 adds a simple encoder.
> 
> This patchset should be applied on next branch.
> 

Please fix your clock, so this patchset does not appear +4h in the
future and on top of other patches...

Best regards,
Krzysztof


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: keith <keith.zhao@starfivetech.com>,
	andrzej.hajda@intel.com, neil.armstrong@linaro.org,
	rfoss@kernel.org, Laurent.pinchart@ideasonboard.com,
	jonas@kwiboo.se, jernej.skrabec@gmail.com,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	hjc@rock-chips.com, heiko@sntech.de, andy.yan@rock-chips.com,
	xingyu.wu@starfivetech.com, p.zabel@pengutronix.de,
	jack.zhu@starfivetech.com, shengyang.chen@starfivetech.com
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 00/10] drm/verisilicon : support DC8200 and inno hdmi
Date: Tue, 21 May 2024 09:18:49 +0200	[thread overview]
Message-ID: <9949da52-c7ec-4a95-b323-8e40ef4af06e@kernel.org> (raw)
In-Reply-To: <20240521105817.3301-1-keith.zhao@starfivetech.com>

On 21/05/2024 12:58, keith wrote:
> Verisilicon/DC8200 display controller IP has 2 display pipes and each 
> pipe support a primary plane and a cursor plane . 
> In addition, there are four overlay planes as two display pipes common resources.
> 
> The first display pipe is bound to the inno HDMI encoder.
> The second display pipe is bound to a simple encoder, which is used to
> find dsi bridge by dts node. 
> 
> Patch 1 adds YAML schema for JH7110 display pipeline.
> 
> Patches 2 to 3 add inno common api and match the ROCKCHIP inno hdmi driver 
> by calling the common api. 
> The collating public interface is based on ROCKCHIP inno hdmi, 
> and it can be resused by JH7110 inno hdmi.
> Those common api are tested on rk-3128 SDK, which kernel version is 4.x. 
> step1, make sure the process is consistent with the latest kernel version.
> step2, just remove the interface and add a common interface. 
> 
> Patches 4 to 8 add kms driver for dc8200 display controller.
> 
> Patch 9 adds inno hdmi support for JH7110 display pipeline.
> 
> Patch 10 adds a simple encoder.
> 
> This patchset should be applied on next branch.
> 

Please fix your clock, so this patchset does not appear +4h in the
future and on top of other patches...

Best regards,
Krzysztof


  reply	other threads:[~2024-05-21  7:19 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21 10:58 [PATCH v4 00/10] drm/verisilicon : support DC8200 and inno hdmi keith
2024-05-21 10:58 ` keith
2024-05-21  7:18 ` Krzysztof Kozlowski [this message]
2024-05-21  7:18   ` Krzysztof Kozlowski
2024-05-21  8:03 ` Heiko Stübner
2024-05-21  8:03   ` Heiko Stübner
2024-05-21 14:55   ` Alex Bee
2024-05-21 14:55     ` Alex Bee
2024-05-21 10:58 ` [PATCH v4 01/10] dt-bindings: display: Add YAML schema for JH7110 display pipeline keith
2024-05-21 10:58   ` keith
2024-05-21  7:30   ` Krzysztof Kozlowski
2024-05-21  7:30     ` Krzysztof Kozlowski
2024-05-21  9:50     ` Keith Zhao
2024-05-21  9:50       ` Keith Zhao
2024-05-21 10:58 ` [PATCH v4 02/10] drm/bridge: add common api for inno hdmi keith
2024-05-21 10:58   ` keith
2024-05-21  9:30   ` Krzysztof Kozlowski
2024-05-21  9:30     ` Krzysztof Kozlowski
2024-05-21 15:36   ` Alex Bee
2024-05-21 15:36     ` Alex Bee
2024-05-21 15:42     ` Laurent Pinchart
2024-05-21 15:42       ` Laurent Pinchart
2024-05-22  5:58       ` Keith Zhao
2024-05-22  5:58         ` Keith Zhao
2024-05-22  7:32         ` Laurent Pinchart
2024-05-22  7:32           ` Laurent Pinchart
2024-06-23 18:42   ` Markus Elfring
2024-05-21 10:58 ` [PATCH v4 03/10] drm/rockchip:hdmi: migrate to use inno-hdmi bridge driver keith
2024-05-21 10:58   ` keith
2024-05-22  7:24   ` Maxime Ripard
2024-05-22  7:24     ` Maxime Ripard
2024-06-23  7:17     ` Keith Zhao
2024-06-24  9:25       ` Maxime Ripard
2024-05-21 10:58 ` [PATCH v4 04/10] drm/vs: Add hardware funcs for vs keith
2024-05-21 10:58   ` keith
2024-05-21 20:50   ` kernel test robot
2024-05-21 20:50     ` kernel test robot
2024-05-21 20:50   ` Dmitry Baryshkov
2024-05-21 20:50     ` Dmitry Baryshkov
2024-06-23  7:16     ` Keith Zhao
2024-06-23 20:51       ` Dmitry Baryshkov
2024-06-25  8:32         ` Keith Zhao
2024-05-21 21:01   ` kernel test robot
2024-05-21 21:01     ` kernel test robot
2024-05-22  1:34   ` kernel test robot
2024-05-22  1:34     ` kernel test robot
2024-05-21 10:58 ` [PATCH v4 05/10] drm/vs: add vs mode config init keith
2024-05-21 10:58   ` keith
2024-05-21 20:52   ` Dmitry Baryshkov
2024-05-21 20:52     ` Dmitry Baryshkov
2024-06-23  7:17     ` Keith Zhao
2024-06-23 20:52       ` Dmitry Baryshkov
2024-05-21 10:58 ` [PATCH v4 06/10] drm/vs: add vs plane api keith
2024-05-21 10:58   ` keith
2024-05-21 20:39   ` kernel test robot
2024-05-21 20:39     ` kernel test robot
2024-05-21 21:06   ` Dmitry Baryshkov
2024-05-21 21:06     ` Dmitry Baryshkov
2024-06-23  7:17     ` Keith Zhao
2024-06-23 20:54       ` Dmitry Baryshkov
2024-05-21 10:58 ` [PATCH v4 07/10] drm/vs: add ctrc fun keith
2024-05-21 10:58   ` keith
2024-05-21 21:08   ` Dmitry Baryshkov
2024-05-21 21:08     ` Dmitry Baryshkov
2024-06-23  7:17     ` Keith Zhao
2024-06-23 20:56       ` Dmitry Baryshkov
2024-05-21 10:58 ` [PATCH v4 08/10] drm/vs: add vs drm master driver keith
2024-05-21 10:58   ` keith
2024-05-21 21:14   ` Dmitry Baryshkov
2024-05-21 21:14     ` Dmitry Baryshkov
2024-06-23  7:16     ` Keith Zhao
2024-06-23 21:07       ` Dmitry Baryshkov
2024-06-25  8:34         ` Keith Zhao
2024-05-21 10:58 ` [PATCH v4 09/10] drm/vs: Innosilicon HDMI support keith
2024-05-21 10:58   ` keith
2024-05-21  9:31   ` Krzysztof Kozlowski
2024-05-21  9:31     ` Krzysztof Kozlowski
2024-05-21 10:58 ` [PATCH v4 10/10] drm/vs: add simple dsi encoder keith
2024-05-21 10:58   ` keith
2024-05-21 15:25   ` Dmitry Baryshkov
2024-05-21 15:25     ` Dmitry Baryshkov
2024-06-23  7:17     ` Keith Zhao
2024-06-23 21:11       ` Dmitry Baryshkov
2024-06-25  8:33         ` Keith Zhao
2024-06-25 10:59           ` Dmitry Baryshkov
2024-05-22  7:29   ` Maxime Ripard
2024-05-22  7:29     ` Maxime Ripard

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=9949da52-c7ec-4a95-b323-8e40ef4af06e@kernel.org \
    --to=krzk@kernel.org \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=andy.yan@rock-chips.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=hjc@rock-chips.com \
    --cc=jack.zhu@starfivetech.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=keith.zhao@starfivetech.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=rfoss@kernel.org \
    --cc=robh@kernel.org \
    --cc=shengyang.chen@starfivetech.com \
    --cc=tzimmermann@suse.de \
    --cc=xingyu.wu@starfivetech.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.