From: Rob Herring <robh@kernel.org>
To: Bo-Chen Chen <rex-bc.chen@mediatek.com>
Cc: chunkuang.hu@kernel.org, p.zabel@pengutronix.de, daniel@ffwll.ch,
krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
airlied@linux.ie, msp@baylibre.com, granquet@baylibre.com,
jitao.shi@mediatek.com, wenst@chromium.org,
angelogioacchino.delregno@collabora.com, ck.hu@mediatek.com,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v11 01/12] dt-bindings: mediatek,dpi: Add DP_INTF compatible
Date: Tue, 14 Jun 2022 14:24:55 -0600 [thread overview]
Message-ID: <20220614202455.GA2415891-robh@kernel.org> (raw)
In-Reply-To: <20220613064841.10481-2-rex-bc.chen@mediatek.com>
On Mon, Jun 13, 2022 at 02:48:30PM +0800, Bo-Chen Chen wrote:
> From: Markus Schneider-Pargmann <msp@baylibre.com>
>
> DP_INTF is similar to DPI but does not have the exact same feature set
> or register layouts.
>
> DP_INTF is the sink of the display pipeline that is connected to the
> DisplayPort controller and encoder unit. It takes the same clocks as
> DPI.
>
> In this patch, we also do these string replacement:
> - s/mediatek/MediaTek/ in title.
> - s/Mediatek/MediaTek/ in description.
>
> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
> Signed-off-by: Guillaume Ranquet <granquet@baylibre.com>
> Signed-off-by: Bo-Chen Chen <rex-bc.chen@mediatek.com>
> ---
> .../bindings/display/mediatek/mediatek,dpi.yaml | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> index 77ee1b923991..ca1b48e78581 100644
> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> @@ -4,16 +4,16 @@
> $id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: mediatek DPI Controller Device Tree Bindings
> +title: MediaTek DPI and DP_INTF Controller
>
> maintainers:
> - CK Hu <ck.hu@mediatek.com>
> - Jitao shi <jitao.shi@mediatek.com>
>
> description: |
> - The Mediatek DPI function block is a sink of the display subsystem and
> - provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel
> - output bus.
> + The MediaTek DPI and DP_INTF function blocks are a sink of the display
> + subsystem and provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a
> + parallel output bus.
>
> properties:
> compatible:
> @@ -24,6 +24,7 @@ properties:
> - mediatek,mt8183-dpi
> - mediatek,mt8186-dpi
> - mediatek,mt8192-dpi
> + - mediatek,mt8195-dp_intf
>
> reg:
> maxItems: 1
> @@ -36,12 +37,14 @@ properties:
> - description: Pixel Clock
> - description: Engine Clock
> - description: DPI PLL
> + - description: Clock gate for PLL
>
> clock-names:
> items:
> - const: pixel
> - const: engine
> - const: pll
> + - const: pll_gate
You just added a new required clock for everyone.
>
> pinctrl-0: true
> pinctrl-1: true
> @@ -55,7 +58,7 @@ properties:
> $ref: /schemas/graph.yaml#/properties/port
> description:
> Output port node. This port should be connected to the input port of an
> - attached HDMI or LVDS encoder chip.
> + attached HDMI, LVDS or DisplayPort encoder chip.
>
> required:
> - compatible
> --
> 2.18.0
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Bo-Chen Chen <rex-bc.chen@mediatek.com>
Cc: chunkuang.hu@kernel.org, granquet@baylibre.com,
jitao.shi@mediatek.com, devicetree@vger.kernel.org,
airlied@linux.ie, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, msp@baylibre.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-mediatek@lists.infradead.org,
krzysztof.kozlowski+dt@linaro.org, wenst@chromium.org,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org,
angelogioacchino.delregno@collabora.com
Subject: Re: [PATCH v11 01/12] dt-bindings: mediatek,dpi: Add DP_INTF compatible
Date: Tue, 14 Jun 2022 14:24:55 -0600 [thread overview]
Message-ID: <20220614202455.GA2415891-robh@kernel.org> (raw)
In-Reply-To: <20220613064841.10481-2-rex-bc.chen@mediatek.com>
On Mon, Jun 13, 2022 at 02:48:30PM +0800, Bo-Chen Chen wrote:
> From: Markus Schneider-Pargmann <msp@baylibre.com>
>
> DP_INTF is similar to DPI but does not have the exact same feature set
> or register layouts.
>
> DP_INTF is the sink of the display pipeline that is connected to the
> DisplayPort controller and encoder unit. It takes the same clocks as
> DPI.
>
> In this patch, we also do these string replacement:
> - s/mediatek/MediaTek/ in title.
> - s/Mediatek/MediaTek/ in description.
>
> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
> Signed-off-by: Guillaume Ranquet <granquet@baylibre.com>
> Signed-off-by: Bo-Chen Chen <rex-bc.chen@mediatek.com>
> ---
> .../bindings/display/mediatek/mediatek,dpi.yaml | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> index 77ee1b923991..ca1b48e78581 100644
> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> @@ -4,16 +4,16 @@
> $id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: mediatek DPI Controller Device Tree Bindings
> +title: MediaTek DPI and DP_INTF Controller
>
> maintainers:
> - CK Hu <ck.hu@mediatek.com>
> - Jitao shi <jitao.shi@mediatek.com>
>
> description: |
> - The Mediatek DPI function block is a sink of the display subsystem and
> - provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel
> - output bus.
> + The MediaTek DPI and DP_INTF function blocks are a sink of the display
> + subsystem and provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a
> + parallel output bus.
>
> properties:
> compatible:
> @@ -24,6 +24,7 @@ properties:
> - mediatek,mt8183-dpi
> - mediatek,mt8186-dpi
> - mediatek,mt8192-dpi
> + - mediatek,mt8195-dp_intf
>
> reg:
> maxItems: 1
> @@ -36,12 +37,14 @@ properties:
> - description: Pixel Clock
> - description: Engine Clock
> - description: DPI PLL
> + - description: Clock gate for PLL
>
> clock-names:
> items:
> - const: pixel
> - const: engine
> - const: pll
> + - const: pll_gate
You just added a new required clock for everyone.
>
> pinctrl-0: true
> pinctrl-1: true
> @@ -55,7 +58,7 @@ properties:
> $ref: /schemas/graph.yaml#/properties/port
> description:
> Output port node. This port should be connected to the input port of an
> - attached HDMI or LVDS encoder chip.
> + attached HDMI, LVDS or DisplayPort encoder chip.
>
> required:
> - compatible
> --
> 2.18.0
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Bo-Chen Chen <rex-bc.chen@mediatek.com>
Cc: chunkuang.hu@kernel.org, p.zabel@pengutronix.de, daniel@ffwll.ch,
krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
airlied@linux.ie, msp@baylibre.com, granquet@baylibre.com,
jitao.shi@mediatek.com, wenst@chromium.org,
angelogioacchino.delregno@collabora.com, ck.hu@mediatek.com,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v11 01/12] dt-bindings: mediatek,dpi: Add DP_INTF compatible
Date: Tue, 14 Jun 2022 14:24:55 -0600 [thread overview]
Message-ID: <20220614202455.GA2415891-robh@kernel.org> (raw)
In-Reply-To: <20220613064841.10481-2-rex-bc.chen@mediatek.com>
On Mon, Jun 13, 2022 at 02:48:30PM +0800, Bo-Chen Chen wrote:
> From: Markus Schneider-Pargmann <msp@baylibre.com>
>
> DP_INTF is similar to DPI but does not have the exact same feature set
> or register layouts.
>
> DP_INTF is the sink of the display pipeline that is connected to the
> DisplayPort controller and encoder unit. It takes the same clocks as
> DPI.
>
> In this patch, we also do these string replacement:
> - s/mediatek/MediaTek/ in title.
> - s/Mediatek/MediaTek/ in description.
>
> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
> Signed-off-by: Guillaume Ranquet <granquet@baylibre.com>
> Signed-off-by: Bo-Chen Chen <rex-bc.chen@mediatek.com>
> ---
> .../bindings/display/mediatek/mediatek,dpi.yaml | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> index 77ee1b923991..ca1b48e78581 100644
> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> @@ -4,16 +4,16 @@
> $id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: mediatek DPI Controller Device Tree Bindings
> +title: MediaTek DPI and DP_INTF Controller
>
> maintainers:
> - CK Hu <ck.hu@mediatek.com>
> - Jitao shi <jitao.shi@mediatek.com>
>
> description: |
> - The Mediatek DPI function block is a sink of the display subsystem and
> - provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel
> - output bus.
> + The MediaTek DPI and DP_INTF function blocks are a sink of the display
> + subsystem and provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a
> + parallel output bus.
>
> properties:
> compatible:
> @@ -24,6 +24,7 @@ properties:
> - mediatek,mt8183-dpi
> - mediatek,mt8186-dpi
> - mediatek,mt8192-dpi
> + - mediatek,mt8195-dp_intf
>
> reg:
> maxItems: 1
> @@ -36,12 +37,14 @@ properties:
> - description: Pixel Clock
> - description: Engine Clock
> - description: DPI PLL
> + - description: Clock gate for PLL
>
> clock-names:
> items:
> - const: pixel
> - const: engine
> - const: pll
> + - const: pll_gate
You just added a new required clock for everyone.
>
> pinctrl-0: true
> pinctrl-1: true
> @@ -55,7 +58,7 @@ properties:
> $ref: /schemas/graph.yaml#/properties/port
> description:
> Output port node. This port should be connected to the input port of an
> - attached HDMI or LVDS encoder chip.
> + attached HDMI, LVDS or DisplayPort encoder chip.
>
> required:
> - compatible
> --
> 2.18.0
>
>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Bo-Chen Chen <rex-bc.chen@mediatek.com>
Cc: chunkuang.hu@kernel.org, p.zabel@pengutronix.de, daniel@ffwll.ch,
krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
airlied@linux.ie, msp@baylibre.com, granquet@baylibre.com,
jitao.shi@mediatek.com, wenst@chromium.org,
angelogioacchino.delregno@collabora.com, ck.hu@mediatek.com,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v11 01/12] dt-bindings: mediatek,dpi: Add DP_INTF compatible
Date: Tue, 14 Jun 2022 14:24:55 -0600 [thread overview]
Message-ID: <20220614202455.GA2415891-robh@kernel.org> (raw)
In-Reply-To: <20220613064841.10481-2-rex-bc.chen@mediatek.com>
On Mon, Jun 13, 2022 at 02:48:30PM +0800, Bo-Chen Chen wrote:
> From: Markus Schneider-Pargmann <msp@baylibre.com>
>
> DP_INTF is similar to DPI but does not have the exact same feature set
> or register layouts.
>
> DP_INTF is the sink of the display pipeline that is connected to the
> DisplayPort controller and encoder unit. It takes the same clocks as
> DPI.
>
> In this patch, we also do these string replacement:
> - s/mediatek/MediaTek/ in title.
> - s/Mediatek/MediaTek/ in description.
>
> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com>
> Signed-off-by: Guillaume Ranquet <granquet@baylibre.com>
> Signed-off-by: Bo-Chen Chen <rex-bc.chen@mediatek.com>
> ---
> .../bindings/display/mediatek/mediatek,dpi.yaml | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> index 77ee1b923991..ca1b48e78581 100644
> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml
> @@ -4,16 +4,16 @@
> $id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: mediatek DPI Controller Device Tree Bindings
> +title: MediaTek DPI and DP_INTF Controller
>
> maintainers:
> - CK Hu <ck.hu@mediatek.com>
> - Jitao shi <jitao.shi@mediatek.com>
>
> description: |
> - The Mediatek DPI function block is a sink of the display subsystem and
> - provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel
> - output bus.
> + The MediaTek DPI and DP_INTF function blocks are a sink of the display
> + subsystem and provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a
> + parallel output bus.
>
> properties:
> compatible:
> @@ -24,6 +24,7 @@ properties:
> - mediatek,mt8183-dpi
> - mediatek,mt8186-dpi
> - mediatek,mt8192-dpi
> + - mediatek,mt8195-dp_intf
>
> reg:
> maxItems: 1
> @@ -36,12 +37,14 @@ properties:
> - description: Pixel Clock
> - description: Engine Clock
> - description: DPI PLL
> + - description: Clock gate for PLL
>
> clock-names:
> items:
> - const: pixel
> - const: engine
> - const: pll
> + - const: pll_gate
You just added a new required clock for everyone.
>
> pinctrl-0: true
> pinctrl-1: true
> @@ -55,7 +58,7 @@ properties:
> $ref: /schemas/graph.yaml#/properties/port
> description:
> Output port node. This port should be connected to the input port of an
> - attached HDMI or LVDS encoder chip.
> + attached HDMI, LVDS or DisplayPort encoder chip.
>
> required:
> - compatible
> --
> 2.18.0
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-14 20:25 UTC|newest]
Thread overview: 124+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 6:48 [PATCH v11 00/12] drm/mediatek: Add MT8195 dp_intf driver Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` [PATCH v11 01/12] dt-bindings: mediatek,dpi: Add DP_INTF compatible Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 13:33 ` Rob Herring
2022-06-13 13:33 ` Rob Herring
2022-06-13 13:33 ` Rob Herring
2022-06-13 13:33 ` [PATCH v11 01/12] dt-bindings: mediatek, dpi: " Rob Herring
2022-06-14 3:05 ` [PATCH v11 01/12] dt-bindings: mediatek,dpi: " CK Hu
2022-06-14 3:05 ` CK Hu
2022-06-14 3:05 ` CK Hu
2022-06-14 3:05 ` CK Hu
2022-06-16 7:58 ` Rex-BC Chen
2022-06-16 7:58 ` Rex-BC Chen
2022-06-16 7:58 ` Rex-BC Chen
2022-06-14 20:24 ` Rob Herring [this message]
2022-06-14 20:24 ` Rob Herring
2022-06-14 20:24 ` Rob Herring
2022-06-14 20:24 ` Rob Herring
2022-06-16 7:55 ` Rex-BC Chen
2022-06-16 7:55 ` Rex-BC Chen
2022-06-16 7:55 ` Rex-BC Chen
2022-06-13 6:48 ` [PATCH v11 02/12] drm/mediatek: dpi: move dpi limits to SoC config Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-14 3:21 ` CK Hu
2022-06-14 3:21 ` CK Hu
2022-06-14 3:21 ` CK Hu
2022-06-14 3:21 ` CK Hu
2022-06-16 10:31 ` Rex-BC Chen
2022-06-16 10:31 ` Rex-BC Chen
2022-06-16 10:31 ` Rex-BC Chen
2022-06-13 6:48 ` [PATCH v11 03/12] drm/mediatek: dpi: implement a CK/DE pol toggle in " Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-14 3:36 ` CK Hu
2022-06-14 3:36 ` CK Hu
2022-06-14 3:36 ` CK Hu
2022-06-14 3:36 ` CK Hu
2022-06-13 6:48 ` [PATCH v11 04/12] drm/mediatek: dpi: implement a swap_input " Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-14 5:27 ` CK Hu
2022-06-14 5:27 ` CK Hu
2022-06-14 5:27 ` CK Hu
2022-06-14 5:27 ` CK Hu
2022-06-16 10:36 ` Rex-BC Chen
2022-06-16 10:36 ` Rex-BC Chen
2022-06-16 10:36 ` Rex-BC Chen
2022-06-13 6:48 ` [PATCH v11 05/12] drm/mediatek: dpi: move dimension mask to " Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` [PATCH v11 06/12] drm/mediatek: dpi: move hvsize_mask " Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` [PATCH v11 07/12] drm/mediatek: dpi: move swap_shift " Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-14 5:38 ` CK Hu
2022-06-14 5:38 ` CK Hu
2022-06-14 5:38 ` CK Hu
2022-06-14 5:38 ` CK Hu
2022-06-13 6:48 ` [PATCH v11 08/12] drm/mediatek: dpi: move the yuv422_en_bit " Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` [PATCH v11 09/12] drm/mediatek: dpi: move the csc_enable bit " Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-14 5:45 ` CK Hu
2022-06-14 5:45 ` CK Hu
2022-06-14 5:45 ` CK Hu
2022-06-14 5:45 ` CK Hu
2022-06-13 6:48 ` [PATCH v11 10/12] drm/mediatek: dpi: Add dpintf support Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 10:55 ` AngeloGioacchino Del Regno
2022-06-13 10:55 ` AngeloGioacchino Del Regno
2022-06-13 10:55 ` AngeloGioacchino Del Regno
2022-06-13 10:55 ` AngeloGioacchino Del Regno
2022-06-16 7:57 ` Rex-BC Chen
2022-06-16 7:57 ` Rex-BC Chen
2022-06-16 7:57 ` Rex-BC Chen
2022-06-14 6:04 ` CK Hu
2022-06-14 6:04 ` CK Hu
2022-06-14 6:04 ` CK Hu
2022-06-14 6:04 ` CK Hu
2022-06-16 9:09 ` Rex-BC Chen
2022-06-16 9:09 ` Rex-BC Chen
2022-06-16 9:09 ` Rex-BC Chen
2022-06-13 6:48 ` [PATCH v11 11/12] drm/mediatek: dpi: Only enable dpi after the bridge is enabled Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-14 6:24 ` CK Hu
2022-06-14 6:24 ` CK Hu
2022-06-14 6:24 ` CK Hu
2022-06-14 6:24 ` CK Hu
2022-06-16 10:49 ` Rex-BC Chen
2022-06-16 10:49 ` Rex-BC Chen
2022-06-16 10:49 ` Rex-BC Chen
2022-06-13 6:48 ` [PATCH v11 12/12] drm/mediatek: dpi: Add matrix_sel helper Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-13 6:48 ` Bo-Chen Chen
2022-06-14 6:20 ` CK Hu
2022-06-14 6:20 ` CK Hu
2022-06-14 6:20 ` CK Hu
2022-06-14 6:20 ` CK Hu
2022-06-16 10:51 ` Rex-BC Chen
2022-06-16 10:51 ` Rex-BC Chen
2022-06-16 10:51 ` Rex-BC Chen
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=20220614202455.GA2415891-robh@kernel.org \
--to=robh@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=airlied@linux.ie \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=granquet@baylibre.com \
--cc=jitao.shi@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=msp@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=rex-bc.chen@mediatek.com \
--cc=wenst@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 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.