From: Marek Vasut <marex@denx.de>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Lucas Stach <l.stach@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
patchwork-lst@pengutronix.de, Sandor Yu <Sandor.yu@nxp.com>,
linux-phy@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Robert Foss <robert.foss@linaro.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: (EXT) [PATCH v0.5 0/9] i.MX8MP HDMI support
Date: Thu, 19 May 2022 02:55:04 +0200 [thread overview]
Message-ID: <85b6a706-79ab-2e50-2549-ce2d70ff8eb2@denx.de> (raw)
In-Reply-To: <2112379.Mh6RI2rZIc@steina-w>
On 5/9/22 11:44, Alexander Stein wrote:
> Hi Lucas,
>
> Am Freitag, 6. Mai 2022, 20:10:25 CEST schrieb Lucas Stach:
>> second round of the i.MX8MP HDMI work. Still not split up into proper
>> parts for merging through the various trees this needs to go into, but
>> should make it easy for people to test.
>>
>> I've worked in the feedback I got from the last round, including fixing
>> the system hang that could happen when the drivers were built as modules.
>>
>> Series is based on linux-next/master, as there are some prerequisite
>> patches in both the drm and imx tree already. The last patch from [1]
>> and the patches from [2] need to be applied. Please note that this series
>> expects the sync polarity from the LCDIF to be set according to the
>> comments I made in [2]. Please test and provide feedback.
>
> Thanks for the 2nd round of HDMI support patches. Sorry I wasn't able to reply
> to your questions, but the PLL locking seems to be gone on my system.
>
> I still get the error
>> imx-lcdif 32fc6000.display-controller: Unknown media bus format 0x200f
>
> To answer the other question on the last patchset
>> Do have a 4k HDMI display connected that wants to do YUV input? That's
>> something I have to admit I didn't test yet and would be likely to
>> cause this bus format selection.
>
> This is a FullHD HDMI monitor, ASUS PB238Q. Apparently the color format is
> YCBCR422. From what I can see is that
> dw_hdmi_bridge_atomic_get_output_bus_fmts() adds MEDIA_BUS_FMT_UYVY8_1X16
> (0x200f) to the output formats. This is then passed to
Try LCDIFv3 v3 patchset I just posted, that should work then.
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Lucas Stach <l.stach@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
patchwork-lst@pengutronix.de, Sandor Yu <Sandor.yu@nxp.com>,
linux-phy@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Robert Foss <robert.foss@linaro.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: (EXT) [PATCH v0.5 0/9] i.MX8MP HDMI support
Date: Thu, 19 May 2022 02:55:04 +0200 [thread overview]
Message-ID: <85b6a706-79ab-2e50-2549-ce2d70ff8eb2@denx.de> (raw)
In-Reply-To: <2112379.Mh6RI2rZIc@steina-w>
On 5/9/22 11:44, Alexander Stein wrote:
> Hi Lucas,
>
> Am Freitag, 6. Mai 2022, 20:10:25 CEST schrieb Lucas Stach:
>> second round of the i.MX8MP HDMI work. Still not split up into proper
>> parts for merging through the various trees this needs to go into, but
>> should make it easy for people to test.
>>
>> I've worked in the feedback I got from the last round, including fixing
>> the system hang that could happen when the drivers were built as modules.
>>
>> Series is based on linux-next/master, as there are some prerequisite
>> patches in both the drm and imx tree already. The last patch from [1]
>> and the patches from [2] need to be applied. Please note that this series
>> expects the sync polarity from the LCDIF to be set according to the
>> comments I made in [2]. Please test and provide feedback.
>
> Thanks for the 2nd round of HDMI support patches. Sorry I wasn't able to reply
> to your questions, but the PLL locking seems to be gone on my system.
>
> I still get the error
>> imx-lcdif 32fc6000.display-controller: Unknown media bus format 0x200f
>
> To answer the other question on the last patchset
>> Do have a 4k HDMI display connected that wants to do YUV input? That's
>> something I have to admit I didn't test yet and would be likely to
>> cause this bus format selection.
>
> This is a FullHD HDMI monitor, ASUS PB238Q. Apparently the color format is
> YCBCR422. From what I can see is that
> dw_hdmi_bridge_atomic_get_output_bus_fmts() adds MEDIA_BUS_FMT_UYVY8_1X16
> (0x200f) to the output formats. This is then passed to
Try LCDIFv3 v3 patchset I just posted, that should work then.
_______________________________________________
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: Marek Vasut <marex@denx.de>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Lucas Stach <l.stach@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
patchwork-lst@pengutronix.de, Sandor Yu <Sandor.yu@nxp.com>,
linux-phy@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Robert Foss <robert.foss@linaro.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: (EXT) [PATCH v0.5 0/9] i.MX8MP HDMI support
Date: Thu, 19 May 2022 02:55:04 +0200 [thread overview]
Message-ID: <85b6a706-79ab-2e50-2549-ce2d70ff8eb2@denx.de> (raw)
In-Reply-To: <2112379.Mh6RI2rZIc@steina-w>
On 5/9/22 11:44, Alexander Stein wrote:
> Hi Lucas,
>
> Am Freitag, 6. Mai 2022, 20:10:25 CEST schrieb Lucas Stach:
>> second round of the i.MX8MP HDMI work. Still not split up into proper
>> parts for merging through the various trees this needs to go into, but
>> should make it easy for people to test.
>>
>> I've worked in the feedback I got from the last round, including fixing
>> the system hang that could happen when the drivers were built as modules.
>>
>> Series is based on linux-next/master, as there are some prerequisite
>> patches in both the drm and imx tree already. The last patch from [1]
>> and the patches from [2] need to be applied. Please note that this series
>> expects the sync polarity from the LCDIF to be set according to the
>> comments I made in [2]. Please test and provide feedback.
>
> Thanks for the 2nd round of HDMI support patches. Sorry I wasn't able to reply
> to your questions, but the PLL locking seems to be gone on my system.
>
> I still get the error
>> imx-lcdif 32fc6000.display-controller: Unknown media bus format 0x200f
>
> To answer the other question on the last patchset
>> Do have a 4k HDMI display connected that wants to do YUV input? That's
>> something I have to admit I didn't test yet and would be likely to
>> cause this bus format selection.
>
> This is a FullHD HDMI monitor, ASUS PB238Q. Apparently the color format is
> YCBCR422. From what I can see is that
> dw_hdmi_bridge_atomic_get_output_bus_fmts() adds MEDIA_BUS_FMT_UYVY8_1X16
> (0x200f) to the output formats. This is then passed to
Try LCDIFv3 v3 patchset I just posted, that should work then.
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Lucas Stach <l.stach@pengutronix.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Sandor Yu <Sandor.yu@nxp.com>,
Robert Foss <robert.foss@linaro.org>,
patchwork-lst@pengutronix.de,
Andrzej Hajda <andrzej.hajda@intel.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-phy@lists.infradead.org, Shawn Guo <shawnguo@kernel.org>
Subject: Re: (EXT) [PATCH v0.5 0/9] i.MX8MP HDMI support
Date: Thu, 19 May 2022 02:55:04 +0200 [thread overview]
Message-ID: <85b6a706-79ab-2e50-2549-ce2d70ff8eb2@denx.de> (raw)
In-Reply-To: <2112379.Mh6RI2rZIc@steina-w>
On 5/9/22 11:44, Alexander Stein wrote:
> Hi Lucas,
>
> Am Freitag, 6. Mai 2022, 20:10:25 CEST schrieb Lucas Stach:
>> second round of the i.MX8MP HDMI work. Still not split up into proper
>> parts for merging through the various trees this needs to go into, but
>> should make it easy for people to test.
>>
>> I've worked in the feedback I got from the last round, including fixing
>> the system hang that could happen when the drivers were built as modules.
>>
>> Series is based on linux-next/master, as there are some prerequisite
>> patches in both the drm and imx tree already. The last patch from [1]
>> and the patches from [2] need to be applied. Please note that this series
>> expects the sync polarity from the LCDIF to be set according to the
>> comments I made in [2]. Please test and provide feedback.
>
> Thanks for the 2nd round of HDMI support patches. Sorry I wasn't able to reply
> to your questions, but the PLL locking seems to be gone on my system.
>
> I still get the error
>> imx-lcdif 32fc6000.display-controller: Unknown media bus format 0x200f
>
> To answer the other question on the last patchset
>> Do have a 4k HDMI display connected that wants to do YUV input? That's
>> something I have to admit I didn't test yet and would be likely to
>> cause this bus format selection.
>
> This is a FullHD HDMI monitor, ASUS PB238Q. Apparently the color format is
> YCBCR422. From what I can see is that
> dw_hdmi_bridge_atomic_get_output_bus_fmts() adds MEDIA_BUS_FMT_UYVY8_1X16
> (0x200f) to the output formats. This is then passed to
Try LCDIFv3 v3 patchset I just posted, that should work then.
next prev parent reply other threads:[~2022-05-19 0:55 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 18:10 [PATCH v0.5 0/9] i.MX8MP HDMI support Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` [PATCH v0.5 1/9] dt-bindings: display: imx: add binding for i.MX8MP HDMI TX Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-09 0:55 ` Marek Vasut
2022-05-09 0:55 ` Marek Vasut
2022-05-09 0:55 ` Marek Vasut
2022-05-09 0:55 ` Marek Vasut
2022-05-10 18:12 ` Rob Herring
2022-05-10 18:12 ` Rob Herring
2022-05-10 18:12 ` Rob Herring
2022-05-10 18:12 ` Rob Herring
2022-05-06 18:10 ` [PATCH v0.5 2/9] drm/imx: add bridge wrapper driver for i.MX8MP DWC HDMI Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` [PATCH v0.5 3/9] dt-bindings: display: imx: add binding for i.MX8MP HDMI PVI Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-06 18:10 ` [PATCH v0.5 4/9] drm/imx: add driver for HDMI TX Parallel Video Interface Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` [PATCH v0.5 5/9] dt-bindings: phy: add binding for the i.MX8MP HDMI PHY Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-06 22:39 ` Rob Herring
2022-05-10 18:14 ` Rob Herring
2022-05-10 18:14 ` Rob Herring
2022-05-10 18:14 ` Rob Herring
2022-05-10 18:14 ` Rob Herring
2022-05-06 18:10 ` [PATCH v0.5 6/9] phy: freescale: add Samsung " Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-09 0:47 ` Marek Vasut
2022-05-09 0:47 ` Marek Vasut
2022-05-09 0:47 ` Marek Vasut
2022-05-09 0:47 ` Marek Vasut
2022-05-09 5:57 ` Vinod Koul
2022-05-09 5:57 ` Vinod Koul
2022-05-09 5:57 ` Vinod Koul
2022-05-09 5:57 ` Vinod Koul
2022-05-06 18:10 ` [PATCH v0.5 7/9] arm64: dts: imx8mp: add HDMI irqsteer Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` [PATCH v0.5 8/9] arm64: dts: imx8mp: add HDMI display pipeline Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` [PATCH v0.5 9/9] arm64: dts: imx8mp-evk: enable HDMI Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-06 18:10 ` Lucas Stach
2022-05-09 9:44 ` (EXT) [PATCH v0.5 0/9] i.MX8MP HDMI support Alexander Stein
2022-05-09 9:44 ` Alexander Stein
2022-05-09 9:44 ` Alexander Stein
2022-05-09 9:44 ` Alexander Stein
2022-05-19 0:55 ` Marek Vasut [this message]
2022-05-19 0:55 ` Marek Vasut
2022-05-19 0:55 ` Marek Vasut
2022-05-19 0:55 ` Marek Vasut
2023-03-20 17:16 ` Tommaso Merciai
2023-03-20 17:16 ` Tommaso Merciai
2023-03-20 17:16 ` Tommaso Merciai
2023-03-20 17:16 ` Tommaso Merciai
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=85b6a706-79ab-2e50-2549-ce2d70ff8eb2@denx.de \
--to=marex@denx.de \
--cc=Sandor.yu@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrzej.hajda@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-phy@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=patchwork-lst@pengutronix.de \
--cc=robert.foss@linaro.org \
--cc=shawnguo@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 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.