From: "Andy Yan" <andyshrk@163.com>
To: "Krzysztof Kozlowski" <krzk@kernel.org>
Cc: robh@kernel.org, iommu@lists.linux.dev, heiko@sntech.de,
devicetree@vger.kernel.org, joro@8bytes.org, hjc@rock-chips.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-phy@lists.infradead.org, vkoul@kernel.org,
detlev.casanova@collabora.com,
linux-arm-kernel@lists.infradead.org,
"Andy Yan" <andy.yan@rock-chips.com>,
linux-rockchip@lists.infradead.org, krzk+dt@kernel.org,
cl@rock-chips.com
Subject: Re:Re: [PATCH v2 5/8] dt-bindings: display: vop2: Add rk3576 support
Date: Tue, 31 Dec 2024 16:43:27 +0800 (CST) [thread overview]
Message-ID: <61d9f4f4.8013.1941be25dc6.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <6pn3qjxotdtpzucpul24yro7ppddezwuizneovqvmgdwyv2j7p@ztg4mqyiqmjf>
Hi Krzysztof,
At 2024-12-31 16:23:39, "Krzysztof Kozlowski" <krzk@kernel.org> wrote:
>On Sun, Dec 29, 2024 at 06:49:38PM +0800, Andy Yan wrote:
>>
>>
>> Hi Krzysztof,
>>
>> At 2024-12-29 18:13:39, "Krzysztof Kozlowski" <krzk@kernel.org> wrote:
>> >On Sat, Dec 28, 2024 at 08:21:48PM +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 v2:
>> >> - describe constraint SOC by SOC, as interrupts of rk3576 is very
>> >> different from others
>> >> - Drop Krzysztof's Reviewed-by, as this version changed a lot.
>> >>
>> >> Changes in v1:
>> >> - ordered by soc name
>> >> - Add description for newly added interrupt
>> >>
>> >> .../display/rockchip/rockchip-vop2.yaml | 70 +++++++++++++++----
>> >> 1 file changed, 56 insertions(+), 14 deletions(-)
>> >>
>> >> diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip-vop2.yaml b/Documentation/devicetree/bindings/display/rockchip/rockchip-vop2.yaml
>> >> index 2531726af306..f28cea4a6d82 100644
>> >> --- a/Documentation/devicetree/bindings/display/rockchip/rockchip-vop2.yaml
>> >> +++ b/Documentation/devicetree/bindings/display/rockchip/rockchip-vop2.yaml
>> >> @@ -20,6 +20,7 @@ properties:
>> >> enum:
>> >> - rockchip,rk3566-vop
>> >> - rockchip,rk3568-vop
>> >> + - rockchip,rk3576-vop
>> >> - rockchip,rk3588-vop
>> >>
>> >> reg:
>> >> @@ -37,10 +38,22 @@ properties:
>> >> - const: gamma-lut
>> >>
>> >> interrupts:
>> >> - maxItems: 1
>> >> - description:
>> >> - The VOP interrupt is shared by several interrupt sources, such as
>> >> - frame start (VSYNC), line flag and other status interrupts.
>> >> + minItems: 1
>> >> + maxItems: 4
>> >> + items:
>> >> + - description:
>> >
>> >That's contradictory. min/max say 1-4, but here you list two interrupts.
>>
>> There are 4 interrupts on rk3576, and the other SOC only have one.
>
>But you listed two interrupts, so where does the "two" come from?
>
>> I am sorry that I am not familiar with this schema language; I have read many
>> other YAML bindings these days and try to write it correctly.
>>
>> Maybe I should not list the interrupts-names here(then list the interrupt-name by soc at allOf: part),
>> like the clocks handles in samsung,usb3-drd-phy.yaml ?
>
>xxx-names are supposed to be fully synced with xxx, so something needs
>to be fixed here. You can of course remove interrupt-names *completely*
>(but not partially, because all properties must be defined in top-level).
Thanks for your explanation, I will send a new version later.
>
>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:[~2024-12-31 9:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 12:21 [PATCH v2 0/8] Add display subsystem dt node on rk3576 Andy Yan
2024-12-28 12:21 ` [PATCH v2 1/8] dt-bindings: soc: rockchip: add rk3576 hdptxphy grf syscon Andy Yan
2024-12-28 12:21 ` [PATCH v2 2/8] dt-bindings: phy: Add rk3576 hdptx phy Andy Yan
2024-12-28 12:21 ` [PATCH v2 3/8] dt-bindings: display: rockchip: Add rk3576 hdmi controller Andy Yan
2024-12-28 12:21 ` [PATCH v2 4/8] dt-bindings: iommu: rockchip: Add Rockchip RK3576 Andy Yan
2024-12-28 12:21 ` [PATCH v2 5/8] dt-bindings: display: vop2: Add rk3576 support Andy Yan
2024-12-28 14:09 ` Rob Herring (Arm)
2024-12-29 10:13 ` Krzysztof Kozlowski
2024-12-29 10:49 ` Andy Yan
2024-12-31 8:23 ` Krzysztof Kozlowski
2024-12-31 8:43 ` Andy Yan [this message]
2024-12-28 12:21 ` [PATCH v2 6/8] arm64: dts: rockchip: Add vop for rk3576 Andy Yan
2024-12-28 12:21 ` [PATCH v2 7/8] arm64: dts: rockchip: Add hdmi " Andy Yan
2024-12-28 12:21 ` [PATCH v2 8/8] arm64: dts: rockchip: Enable hdmi display on sige5 Andy Yan
2024-12-28 18:36 ` [PATCH v2 0/8] Add display subsystem dt node on rk3576 Heiko Stübner
2024-12-29 6:48 ` Andy Yan
2024-12-29 14:35 ` Heiko Stübner
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=61d9f4f4.8013.1941be25dc6.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=andy.yan@rock-chips.com \
--cc=cl@rock-chips.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=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=vkoul@kernel.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