From: "Heiko Stübner" <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>, Sascha Hauer <s.hauer@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
kernel@pengutronix.de, Andy Yan <andy.yan@rock-chips.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
Sandy Huang <hjc@rock-chips.com>,
Peter Geis <pgwipeout@gmail.com>
Subject: Re: [PATCH v5 19/23] arm64: dts: rockchip: rk3568-evb: Enable VOP2 and hdmi
Date: Thu, 10 Feb 2022 14:51:15 +0100 [thread overview]
Message-ID: <2434650.DyAAmxEfAj@diego> (raw)
In-Reply-To: <20220210133759.GZ18637@pengutronix.de>
Am Donnerstag, 10. Februar 2022, 14:37:59 CET schrieb Sascha Hauer:
> On Thu, Feb 10, 2022 at 02:15:17PM +0100, Johan Jonker wrote:
> >
> >
> > On 2/10/22 12:47, Sascha Hauer wrote:
> > > On Thu, Feb 10, 2022 at 01:10:32AM +0100, Johan Jonker wrote:
> > >> Hi Sascha,
> > >>
> > >> Something with port and endpoint gives notifications.
> > >> Somehow with the conversion of rockchip,dw-hdmi.txt to YAML not all SoC
> > >> options were checked/covered (see rk3328 and rk3568).
> > >>
> > >> Allow multiple vop:
> > >> port or
> > >> port@0
> > >> 1x vop -> endpoint
> > >>
> > >> 2x vop -> endpoint@0
> > >> -> endpoint@1
> > >>
> > >> Also allow for connector:
> > >> (not all existing DT have this yet)
> > >> port@1
> > >> -> endpoint
> > >>
> > >> See also at graph.yaml
> > >
> > > Ok, let me see if I get this right. The HDMI can either have one or two
> > > ports. It has one when the HDMI connector is not described in the device
> > > tree and two when it is. Also the first (or only) port can have one or
> > > two endpoints. It has one endpoint when the SoC has a single VOP and two
> > > endpoints when the SoC has two VOPs.
> > >
> > > It's been a painful morning because my YAML knowledge is fairly limited,
> > > but here's what I came up with:
> > >
> > > ports:
> > > $ref: /schemas/graph.yaml#/properties/ports
> > > unevaluatedProperties: false
> > > patternProperties:
> > > "^port(@0)?$":
> > > $ref: /schemas/graph.yaml#/properties/port
> > > description: Input of the DWC HDMI TX
> > > properties:
> > > endpoint:
> > > description: Connection to the VOP
> > > endpoint@0:
> > > description: Connection to the VOPB
> > > endpoint@1:
> > > description: Connection to the VOPL
> > > properties:
> > > port@1:
> > > $ref: /schemas/graph.yaml#/properties/port
> > > description: Output of the DWC HDMI TX
> > >
> > > Does this look sane to you? With this a make dtbs_check on this binding
> > > doesn't generate warnings anymore, and even better it does generate
> > > warnings when I add some wrong nodes/properties to the dts files.
> >
> > Hi,
> >
> > Send a patch to rob+dt and he will let you know... ;)
>
> ;)
>
> >
> > Also could you test the ARM branch as well just for sure with:
> > ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make dtbs_check
> > DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml
>
> That works fine except for iahb and isfr clocks in the wrong order in
> arch/arm/boot/dts/rk322x.dtsi.
>
> >
> > Could you group your serie a bit:
> > dt-bindings
> > drm patches
> > dts changes
>
> That's the order I originally had. Heiko asked me to put the
> bindings, dts changes and driver patches together dor each topic.
with the background being that I can judge which parts are essentially
ready and possibly apply parts of a larger series without waiting
for everything to be ready.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>, Sascha Hauer <s.hauer@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
kernel@pengutronix.de, Andy Yan <andy.yan@rock-chips.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
Sandy Huang <hjc@rock-chips.com>,
Peter Geis <pgwipeout@gmail.com>
Subject: Re: [PATCH v5 19/23] arm64: dts: rockchip: rk3568-evb: Enable VOP2 and hdmi
Date: Thu, 10 Feb 2022 14:51:15 +0100 [thread overview]
Message-ID: <2434650.DyAAmxEfAj@diego> (raw)
In-Reply-To: <20220210133759.GZ18637@pengutronix.de>
Am Donnerstag, 10. Februar 2022, 14:37:59 CET schrieb Sascha Hauer:
> On Thu, Feb 10, 2022 at 02:15:17PM +0100, Johan Jonker wrote:
> >
> >
> > On 2/10/22 12:47, Sascha Hauer wrote:
> > > On Thu, Feb 10, 2022 at 01:10:32AM +0100, Johan Jonker wrote:
> > >> Hi Sascha,
> > >>
> > >> Something with port and endpoint gives notifications.
> > >> Somehow with the conversion of rockchip,dw-hdmi.txt to YAML not all SoC
> > >> options were checked/covered (see rk3328 and rk3568).
> > >>
> > >> Allow multiple vop:
> > >> port or
> > >> port@0
> > >> 1x vop -> endpoint
> > >>
> > >> 2x vop -> endpoint@0
> > >> -> endpoint@1
> > >>
> > >> Also allow for connector:
> > >> (not all existing DT have this yet)
> > >> port@1
> > >> -> endpoint
> > >>
> > >> See also at graph.yaml
> > >
> > > Ok, let me see if I get this right. The HDMI can either have one or two
> > > ports. It has one when the HDMI connector is not described in the device
> > > tree and two when it is. Also the first (or only) port can have one or
> > > two endpoints. It has one endpoint when the SoC has a single VOP and two
> > > endpoints when the SoC has two VOPs.
> > >
> > > It's been a painful morning because my YAML knowledge is fairly limited,
> > > but here's what I came up with:
> > >
> > > ports:
> > > $ref: /schemas/graph.yaml#/properties/ports
> > > unevaluatedProperties: false
> > > patternProperties:
> > > "^port(@0)?$":
> > > $ref: /schemas/graph.yaml#/properties/port
> > > description: Input of the DWC HDMI TX
> > > properties:
> > > endpoint:
> > > description: Connection to the VOP
> > > endpoint@0:
> > > description: Connection to the VOPB
> > > endpoint@1:
> > > description: Connection to the VOPL
> > > properties:
> > > port@1:
> > > $ref: /schemas/graph.yaml#/properties/port
> > > description: Output of the DWC HDMI TX
> > >
> > > Does this look sane to you? With this a make dtbs_check on this binding
> > > doesn't generate warnings anymore, and even better it does generate
> > > warnings when I add some wrong nodes/properties to the dts files.
> >
> > Hi,
> >
> > Send a patch to rob+dt and he will let you know... ;)
>
> ;)
>
> >
> > Also could you test the ARM branch as well just for sure with:
> > ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make dtbs_check
> > DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml
>
> That works fine except for iahb and isfr clocks in the wrong order in
> arch/arm/boot/dts/rk322x.dtsi.
>
> >
> > Could you group your serie a bit:
> > dt-bindings
> > drm patches
> > dts changes
>
> That's the order I originally had. Heiko asked me to put the
> bindings, dts changes and driver patches together dor each topic.
with the background being that I can judge which parts are essentially
ready and possibly apply parts of a larger series without waiting
for everything to be ready.
_______________________________________________
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: "Heiko Stübner" <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>, Sascha Hauer <s.hauer@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
kernel@pengutronix.de, Andy Yan <andy.yan@rock-chips.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
Sandy Huang <hjc@rock-chips.com>,
Peter Geis <pgwipeout@gmail.com>
Subject: Re: [PATCH v5 19/23] arm64: dts: rockchip: rk3568-evb: Enable VOP2 and hdmi
Date: Thu, 10 Feb 2022 14:51:15 +0100 [thread overview]
Message-ID: <2434650.DyAAmxEfAj@diego> (raw)
In-Reply-To: <20220210133759.GZ18637@pengutronix.de>
Am Donnerstag, 10. Februar 2022, 14:37:59 CET schrieb Sascha Hauer:
> On Thu, Feb 10, 2022 at 02:15:17PM +0100, Johan Jonker wrote:
> >
> >
> > On 2/10/22 12:47, Sascha Hauer wrote:
> > > On Thu, Feb 10, 2022 at 01:10:32AM +0100, Johan Jonker wrote:
> > >> Hi Sascha,
> > >>
> > >> Something with port and endpoint gives notifications.
> > >> Somehow with the conversion of rockchip,dw-hdmi.txt to YAML not all SoC
> > >> options were checked/covered (see rk3328 and rk3568).
> > >>
> > >> Allow multiple vop:
> > >> port or
> > >> port@0
> > >> 1x vop -> endpoint
> > >>
> > >> 2x vop -> endpoint@0
> > >> -> endpoint@1
> > >>
> > >> Also allow for connector:
> > >> (not all existing DT have this yet)
> > >> port@1
> > >> -> endpoint
> > >>
> > >> See also at graph.yaml
> > >
> > > Ok, let me see if I get this right. The HDMI can either have one or two
> > > ports. It has one when the HDMI connector is not described in the device
> > > tree and two when it is. Also the first (or only) port can have one or
> > > two endpoints. It has one endpoint when the SoC has a single VOP and two
> > > endpoints when the SoC has two VOPs.
> > >
> > > It's been a painful morning because my YAML knowledge is fairly limited,
> > > but here's what I came up with:
> > >
> > > ports:
> > > $ref: /schemas/graph.yaml#/properties/ports
> > > unevaluatedProperties: false
> > > patternProperties:
> > > "^port(@0)?$":
> > > $ref: /schemas/graph.yaml#/properties/port
> > > description: Input of the DWC HDMI TX
> > > properties:
> > > endpoint:
> > > description: Connection to the VOP
> > > endpoint@0:
> > > description: Connection to the VOPB
> > > endpoint@1:
> > > description: Connection to the VOPL
> > > properties:
> > > port@1:
> > > $ref: /schemas/graph.yaml#/properties/port
> > > description: Output of the DWC HDMI TX
> > >
> > > Does this look sane to you? With this a make dtbs_check on this binding
> > > doesn't generate warnings anymore, and even better it does generate
> > > warnings when I add some wrong nodes/properties to the dts files.
> >
> > Hi,
> >
> > Send a patch to rob+dt and he will let you know... ;)
>
> ;)
>
> >
> > Also could you test the ARM branch as well just for sure with:
> > ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make dtbs_check
> > DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml
>
> That works fine except for iahb and isfr clocks in the wrong order in
> arch/arm/boot/dts/rk322x.dtsi.
>
> >
> > Could you group your serie a bit:
> > dt-bindings
> > drm patches
> > dts changes
>
> That's the order I originally had. Heiko asked me to put the
> bindings, dts changes and driver patches together dor each topic.
with the background being that I can judge which parts are essentially
ready and possibly apply parts of a larger series without waiting
for everything to be ready.
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>, Sascha Hauer <s.hauer@pengutronix.de>
Cc: devicetree@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Peter Geis <pgwipeout@gmail.com>,
Sandy Huang <hjc@rock-chips.com>,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org,
Michael Riesch <michael.riesch@wolfvision.net>,
kernel@pengutronix.de, Andy Yan <andy.yan@rock-chips.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 19/23] arm64: dts: rockchip: rk3568-evb: Enable VOP2 and hdmi
Date: Thu, 10 Feb 2022 14:51:15 +0100 [thread overview]
Message-ID: <2434650.DyAAmxEfAj@diego> (raw)
In-Reply-To: <20220210133759.GZ18637@pengutronix.de>
Am Donnerstag, 10. Februar 2022, 14:37:59 CET schrieb Sascha Hauer:
> On Thu, Feb 10, 2022 at 02:15:17PM +0100, Johan Jonker wrote:
> >
> >
> > On 2/10/22 12:47, Sascha Hauer wrote:
> > > On Thu, Feb 10, 2022 at 01:10:32AM +0100, Johan Jonker wrote:
> > >> Hi Sascha,
> > >>
> > >> Something with port and endpoint gives notifications.
> > >> Somehow with the conversion of rockchip,dw-hdmi.txt to YAML not all SoC
> > >> options were checked/covered (see rk3328 and rk3568).
> > >>
> > >> Allow multiple vop:
> > >> port or
> > >> port@0
> > >> 1x vop -> endpoint
> > >>
> > >> 2x vop -> endpoint@0
> > >> -> endpoint@1
> > >>
> > >> Also allow for connector:
> > >> (not all existing DT have this yet)
> > >> port@1
> > >> -> endpoint
> > >>
> > >> See also at graph.yaml
> > >
> > > Ok, let me see if I get this right. The HDMI can either have one or two
> > > ports. It has one when the HDMI connector is not described in the device
> > > tree and two when it is. Also the first (or only) port can have one or
> > > two endpoints. It has one endpoint when the SoC has a single VOP and two
> > > endpoints when the SoC has two VOPs.
> > >
> > > It's been a painful morning because my YAML knowledge is fairly limited,
> > > but here's what I came up with:
> > >
> > > ports:
> > > $ref: /schemas/graph.yaml#/properties/ports
> > > unevaluatedProperties: false
> > > patternProperties:
> > > "^port(@0)?$":
> > > $ref: /schemas/graph.yaml#/properties/port
> > > description: Input of the DWC HDMI TX
> > > properties:
> > > endpoint:
> > > description: Connection to the VOP
> > > endpoint@0:
> > > description: Connection to the VOPB
> > > endpoint@1:
> > > description: Connection to the VOPL
> > > properties:
> > > port@1:
> > > $ref: /schemas/graph.yaml#/properties/port
> > > description: Output of the DWC HDMI TX
> > >
> > > Does this look sane to you? With this a make dtbs_check on this binding
> > > doesn't generate warnings anymore, and even better it does generate
> > > warnings when I add some wrong nodes/properties to the dts files.
> >
> > Hi,
> >
> > Send a patch to rob+dt and he will let you know... ;)
>
> ;)
>
> >
> > Also could you test the ARM branch as well just for sure with:
> > ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make dtbs_check
> > DT_SCHEMA_FILES=Documentation/devicetree/bindings/display/rockchip/rockchip,dw-hdmi.yaml
>
> That works fine except for iahb and isfr clocks in the wrong order in
> arch/arm/boot/dts/rk322x.dtsi.
>
> >
> > Could you group your serie a bit:
> > dt-bindings
> > drm patches
> > dts changes
>
> That's the order I originally had. Heiko asked me to put the
> bindings, dts changes and driver patches together dor each topic.
with the background being that I can judge which parts are essentially
ready and possibly apply parts of a larger series without waiting
for everything to be ready.
next prev parent reply other threads:[~2022-02-10 13:51 UTC|newest]
Thread overview: 182+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 9:53 [PATCH v5 00/23] drm/rockchip: RK356x VOP2 support Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 01/23] drm/encoder: Add of_graph port to struct drm_encoder Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 10:07 ` Sascha Hauer
2022-02-09 10:07 ` Sascha Hauer
2022-02-09 10:07 ` Sascha Hauer
2022-02-09 10:07 ` Sascha Hauer
2022-02-09 11:12 ` Jani Nikula
2022-02-09 11:12 ` Jani Nikula
2022-02-09 11:12 ` Jani Nikula
2022-02-09 11:12 ` Jani Nikula
2022-02-10 11:52 ` Sascha Hauer
2022-02-10 11:52 ` Sascha Hauer
2022-02-10 11:52 ` Sascha Hauer
2022-02-10 11:52 ` Sascha Hauer
2022-02-10 15:22 ` Sascha Hauer
2022-02-10 15:22 ` Sascha Hauer
2022-02-10 15:22 ` Sascha Hauer
2022-02-10 15:22 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 02/23] drm/rockchip: dw_hdmi: Do not leave clock enabled in error case Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 10:03 ` Heiko Stübner
2022-02-09 10:03 ` Heiko Stübner
2022-02-09 10:03 ` Heiko Stübner
2022-02-09 10:03 ` Heiko Stübner
2022-02-09 9:53 ` [PATCH v5 03/23] drm/rockchip: dw_hdmi: rename vpll clock to reference clock Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 04/23] dt-bindings: display: rockchip: dw-hdmi: use "ref" as clock name Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 05/23] arm64: dts: rockchip: rk3399: rename HDMI ref clock to 'ref' Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 06/23] drm/rockchip: dw_hdmi: add rk3568 support Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 07/23] dt-bindings: display: rockchip: dw-hdmi: Add compatible for rk3568 HDMI Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 08/23] drm/rockchip: dw_hdmi: add regulator support Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 09/23] dt-bindings: display: rockchip: dw-hdmi: Add " Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 10/23] drm/rockchip: dw_hdmi: Add support for hclk Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-15 19:50 ` Dmitry Osipenko
2022-02-15 19:50 ` Dmitry Osipenko
2022-02-15 19:50 ` Dmitry Osipenko
2022-02-15 19:50 ` Dmitry Osipenko
2022-02-09 9:53 ` [PATCH v5 11/23] dt-bindings: display: rockchip: dw-hdmi: Add additional clock Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 12/23] drm/rockchip: dw_hdmi: Use auto-generated tables Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 10:06 ` Heiko Stübner
2022-02-09 10:06 ` Heiko Stübner
2022-02-09 10:06 ` Heiko Stübner
2022-02-09 10:06 ` Heiko Stübner
2022-02-09 9:53 ` [PATCH v5 13/23] drm/rockchip: dw_hdmi: drop mode_valid hook Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 14/23] drm/rockchip: dw_hdmi: Set cur_ctr to 0 always Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 15/23] drm/rockchip: dw_hdmi: add default 594Mhz clk for 4K@60hz Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 16/23] dt-bindings: display: rockchip: dw-hdmi: Make unwedge pinctrl optional Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 17/23] arm64: dts: rockchip: rk356x: Add VOP2 nodes Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 18/23] arm64: dts: rockchip: rk356x: Add HDMI nodes Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 19/23] arm64: dts: rockchip: rk3568-evb: Enable VOP2 and hdmi Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-10 0:10 ` Johan Jonker
2022-02-10 0:10 ` Johan Jonker
2022-02-10 0:10 ` Johan Jonker
2022-02-10 0:10 ` Johan Jonker
2022-02-10 11:47 ` Sascha Hauer
2022-02-10 11:47 ` Sascha Hauer
2022-02-10 11:47 ` Sascha Hauer
2022-02-10 11:47 ` Sascha Hauer
2022-02-10 13:15 ` Johan Jonker
2022-02-10 13:15 ` Johan Jonker
2022-02-10 13:15 ` Johan Jonker
2022-02-10 13:15 ` Johan Jonker
2022-02-10 13:37 ` Sascha Hauer
2022-02-10 13:37 ` Sascha Hauer
2022-02-10 13:37 ` Sascha Hauer
2022-02-10 13:37 ` Sascha Hauer
2022-02-10 13:51 ` Heiko Stübner [this message]
2022-02-10 13:51 ` Heiko Stübner
2022-02-10 13:51 ` Heiko Stübner
2022-02-10 13:51 ` Heiko Stübner
2022-02-09 9:53 ` [PATCH v5 20/23] arm64: dts: rockchip: enable vop2 and hdmi tx on quartz64a Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 21/23] drm/rockchip: Make VOP driver optional Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` [PATCH v5 22/23] drm: rockchip: Add VOP2 driver Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 20:13 ` Aw: " Frank Wunderlich
2022-02-09 20:13 ` Frank Wunderlich
2022-02-09 20:13 ` Frank Wunderlich
2022-02-09 20:13 ` Frank Wunderlich
2022-02-10 6:50 ` Michael Riesch
2022-02-10 6:50 ` Michael Riesch
2022-02-10 6:50 ` Michael Riesch
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-15 19:47 ` Dmitry Osipenko
2022-02-16 10:39 ` Dmitry Osipenko
2022-02-16 10:39 ` Dmitry Osipenko
2022-02-16 10:39 ` Dmitry Osipenko
2022-02-16 10:39 ` Dmitry Osipenko
2022-02-16 11:22 ` Sascha Hauer
2022-02-16 11:22 ` Sascha Hauer
2022-02-16 11:22 ` Sascha Hauer
2022-02-16 11:22 ` Sascha Hauer
2022-02-16 12:23 ` Dmitry Osipenko
2022-02-16 12:23 ` Dmitry Osipenko
2022-02-16 12:23 ` Dmitry Osipenko
2022-02-16 12:23 ` Dmitry Osipenko
2022-02-09 9:53 ` [PATCH v5 23/23] dt-bindings: display: rockchip: Add binding for VOP2 Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 9:53 ` Sascha Hauer
2022-02-09 18:56 ` Rob Herring
2022-02-09 18:56 ` Rob Herring
2022-02-09 18:56 ` Rob Herring
2022-02-09 18:56 ` Rob Herring
2022-02-09 17:44 ` Aw: [PATCH v5 00/23] drm/rockchip: RK356x VOP2 support Frank Wunderlich
2022-02-09 17:44 ` Frank Wunderlich
2022-02-09 17:44 ` Frank Wunderlich
2022-02-09 17:44 ` Frank Wunderlich
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=2434650.DyAAmxEfAj@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=benjamin.gaignard@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--cc=s.hauer@pengutronix.de \
/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.