From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andy Yan <andyshrk@163.com>
Cc: heiko@sntech.de, hjc@rock-chips.com, krzk+dt@kernel.org,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
derek.foreman@collabora.com, detlev.casanova@collabora.com,
daniel@fooishbar.org, robh@kernel.org,
sebastian.reichel@collabora.com,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v12 12/13] dt-bindings: display: vop2: Add rk3576 support
Date: Wed, 22 Jan 2025 11:29:14 +0100 [thread overview]
Message-ID: <09b3089b-bd44-4993-8377-f191c4a669c4@kernel.org> (raw)
In-Reply-To: <76fe64e1.7132.1948d81c1f4.Coremail.andyshrk@163.com>
On 22/01/2025 11:14, Andy Yan wrote:
> Hi,
>
> At 2025-01-22 16:04:59, "Krzysztof Kozlowski" <krzk@kernel.org> wrote:
>> On Tue, Jan 21, 2025 at 06:34:57PM +0800, Andy Yan wrote:
>>> From: Andy Yan <andy.yan@rock-chips.com>
>>>
>>> Add vop found on rk3576, the main difference between rk3576 and the
>>> previous vop is that each VP has its own interrupt line.
>>>
>>> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>>>
>>> ---
>>>
>>> Changes in v12:
>>> - Split from patch 10/13
>>
>> Order your patches finally. It's v12 and you still send binding after
>> the user. Read carefully submitting bindings/patches.
>
> What do you mean by "sending binding after user" here?
> I think PATCH 1~9 are fix and preparations, PATCH 13("drm/rockchip: vop2: Add support for rk3576")
> is the user that uses the new binding.
Ah, my bad. I thought that's the last one.
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-01-22 10:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 10:32 [PATCH v12 00/13] VOP Support for rk3576 Andy Yan
2025-01-21 10:32 ` [PATCH v12 01/13] drm/rockchip: vop2: use devm_regmap_field_alloc for cluster-regs Andy Yan
2025-01-21 10:32 ` [PATCH v12 02/13] drm/rockchip: vop2: Rename TRANSFORM_OFFSET to TRANSFORM_OFFS Andy Yan
2025-01-21 10:32 ` [PATCH v12 03/13] drm/rockchip: vop2: Add platform specific callback Andy Yan
2025-01-21 10:32 ` [PATCH v12 04/13] drm/rockchip: vop2: Merge vop2_cluster/esmart_init function Andy Yan
2025-01-21 10:32 ` [PATCH v12 05/13] drm/rockchip: vop2: Support for different layer select configuration between VPs Andy Yan
2025-01-21 10:32 ` [PATCH v12 06/13] drm/rockchip: vop2: Introduce vop hardware version Andy Yan
2025-01-21 10:32 ` [PATCH v12 07/13] drm/rockchip: vop2: Register the primary plane and overlay plane separately Andy Yan
2025-01-21 10:32 ` [PATCH v12 08/13] drm/rockchip: vop2: Set plane possible crtcs by possible vp mask Andy Yan
2025-01-21 10:32 ` [PATCH v12 09/13] drm/rockchip: vop2: Add uv swap for cluster window Andy Yan
2025-01-21 10:32 ` [PATCH v12 10/13] dt-bindings: display: vop2: describe constraint SoC by SoC Andy Yan
2025-01-22 8:02 ` Krzysztof Kozlowski
2025-01-21 10:34 ` [PATCH v12 11/13] dt-bindings: display: vop2: Add missing rockchip,grf propertie for rk3566/8 Andy Yan
2025-01-22 8:03 ` Krzysztof Kozlowski
2025-01-22 9:29 ` Andy Yan
2025-01-22 9:43 ` Krzysztof Kozlowski
2025-01-22 9:52 ` Andy Yan
2025-01-21 10:34 ` [PATCH v12 12/13] dt-bindings: display: vop2: Add rk3576 support Andy Yan
2025-01-22 8:04 ` Krzysztof Kozlowski
2025-01-22 9:46 ` Andy Yan
2025-01-22 9:55 ` Krzysztof Kozlowski
2025-01-23 8:10 ` Andy Yan
2025-01-22 10:14 ` Andy Yan
2025-01-22 10:29 ` Krzysztof Kozlowski [this message]
2025-01-21 10:35 ` [PATCH v12 13/13] drm/rockchip: vop2: Add support for rk3576 Andy Yan
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=09b3089b-bd44-4993-8377-f191c4a669c4@kernel.org \
--to=krzk@kernel.org \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=daniel@fooishbar.org \
--cc=derek.foreman@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox