From: Frank Li <Frank.li@nxp.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/10] arm64: dts: imx8mp-skov: use I2C5 for DDC
Date: Thu, 19 Dec 2024 14:27:28 -0500 [thread overview]
Message-ID: <Z2RzoITPUmZFoX09@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <a30baba6-6252-4c69-b6a7-e4099e823920@pengutronix.de>
On Thu, Dec 19, 2024 at 06:43:56PM +0100, Ahmad Fatoum wrote:
> Hello Frank,
>
> On 19.12.24 18:34, Frank Li wrote:
> > On Thu, Dec 19, 2024 at 08:25:27AM +0100, Ahmad Fatoum wrote:
> >> The HDMI DDC pads can be muxed either to an i.MX I2C controller or
> >> to a limited I2C controller within the Designware HDMI bridge.
> >>
> >> So far we muxed the pads to the HDMI bridge, but the i.MX I2C controller
> >> is the better choice:
> >
> > Switch to the i.MX I2C controller because
> >
> >>
> >> - We use DDC/CI commands for display brightness configuration, but the
> >> Linux driver refuses[1] transfers to/from address 0x37, because the
> >> controller doesn't support multi-byte requests.
> >
> > Designware HDMI Limited I2C controller doesn't support multi-byte
> > requests and display brightness configuration by DDC/CI command need it.
> >
> >>
> >> - The driver doesn't support I2C bus recovery, but we need that,
> >> because some HDMI panels used with the board can be flaky.
> >
> > Designware HDMI Limited I2C controller doesn't support I2C bus
> > recovery.
> >
> >>
> >> As the i.MX I2C controller doesn't have either of these limitations,
> >> let's make use of it instead.
> >
> > Reduntant. can be removed.
>
> Sorry, I am very much open to review feedback, but I fail to see how
> your subjective take improves things.
Ref https://docs.kernel.org/process/submitting-patches.html
"Describe your changes in imperative mood, e.g. “make xyzzy do frotz”
instead of “[This patch] makes xyzzy do frotz” or “[I] changed xyzzy to do
frotz”, as if you are giving orders to the codebase to change its behaviour."
Avoid use "we(same as "I" in above example) ..."
Frank
>
> Thanks,
> Ahmad
>
>
>
>
> >
> > Frank
> >>
> >> [1]: https://lore.kernel.org/all/20190722181945.244395-1-mka@chromium.org/
> >>
> >> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> >> ---
> >> .../boot/dts/freescale/imx8mp-skov-revb-hdmi.dts | 26 ++++++++++++++++++++--
> >> 1 file changed, 24 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-skov-revb-hdmi.dts b/arch/arm64/boot/dts/freescale/imx8mp-skov-revb-hdmi.dts
> >> index c1ca69da3cb8..206116be8166 100644
> >> --- a/arch/arm64/boot/dts/freescale/imx8mp-skov-revb-hdmi.dts
> >> +++ b/arch/arm64/boot/dts/freescale/imx8mp-skov-revb-hdmi.dts
> >> @@ -9,12 +9,34 @@ / {
> >> compatible = "skov,imx8mp-skov-revb-hdmi", "fsl,imx8mp";
> >> };
> >>
> >> +&i2c5 {
> >> + pinctrl-names = "default", "gpio";
> >> + pinctrl-0 = <&pinctrl_i2c5>;
> >> + pinctrl-1 = <&pinctrl_i2c5_gpio>;
> >> + scl-gpios = <&gpio3 26 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> >> + sda-gpios = <&gpio3 27 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> >> + clock-frequency = <100000>;
> >> + status = "okay";
> >> +};
> >> +
> >> &iomuxc {
> >> pinctrl_hdmi: hdmigrp {
> >> fsl,pins = <
> >> - MX8MP_IOMUXC_HDMI_DDC_SCL__HDMIMIX_HDMI_SCL 0x1c3
> >> - MX8MP_IOMUXC_HDMI_DDC_SDA__HDMIMIX_HDMI_SDA 0x1c3
> >> MX8MP_IOMUXC_HDMI_HPD__HDMIMIX_HDMI_HPD 0x19
> >> >;
> >> };
> >> +
> >> + pinctrl_i2c5: i2c5grp {
> >> + fsl,pins = <
> >> + MX8MP_IOMUXC_HDMI_DDC_SCL__I2C5_SCL 0x400001c2
> >> + MX8MP_IOMUXC_HDMI_DDC_SDA__I2C5_SDA 0x400001c2
> >> + >;
> >> + };
> >> +
> >> + pinctrl_i2c5_gpio: i2c5gpiogrp {
> >> + fsl,pins = <
> >> + MX8MP_IOMUXC_HDMI_DDC_SCL__GPIO3_IO26 0x400001c2
> >> + MX8MP_IOMUXC_HDMI_DDC_SDA__GPIO3_IO27 0x400001c2
> >> + >;
> >> + };
> >> };
> >>
> >> --
> >> 2.39.5
> >>
> >
>
>
> --
> Pengutronix e.K. | |
> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-12-19 19:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 7:25 [PATCH 00/10] arm64: dts: imx8mp-skov: flesh out device trees Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 01/10] arm64: dts: imx8mp-skov: correct PMIC board limits Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 02/10] arm64: dts: imx8mp-skov: operate CPU at 850 mV by default Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 03/10] arm64: dts: imx8mp-skov: use I2C5 for DDC Ahmad Fatoum
2024-12-19 17:34 ` Frank Li
2024-12-19 17:43 ` Ahmad Fatoum
2024-12-19 19:27 ` Frank Li [this message]
2025-01-06 15:27 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 04/10] arm64: dts: imx8mp-skov: describe HDMI display pipeline Ahmad Fatoum
2024-12-19 17:35 ` Frank Li
2024-12-19 17:40 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 05/10] dt-bindings: display/lvds-codec: add ti,sn65lvds822 Ahmad Fatoum
2024-12-31 1:04 ` Rob Herring (Arm)
2024-12-19 7:25 ` [PATCH 06/10] arm64: dts: imx8mp-skov: describe LVDS display pipeline Ahmad Fatoum
2024-12-19 17:37 ` Frank Li
2024-12-19 17:45 ` Ahmad Fatoum
2024-12-19 19:24 ` Frank Li
2025-01-06 15:36 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 07/10] arm64: dts: imx8mp-skov: configure uart1 for RS485 Ahmad Fatoum
2024-12-19 17:42 ` Frank Li
2024-12-19 17:47 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 08/10] arm64: dts: imx8mp-skov: describe mains fail detection Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 09/10] arm64: dts: imx8mp-skov: fix phy-mode Ahmad Fatoum
2024-12-19 17:45 ` Frank Li
2024-12-19 17:49 ` Ahmad Fatoum
2024-12-19 7:25 ` [PATCH 10/10] arm64: dts: imx8mp-skov: increase I2C clock frequency for RTC Ahmad Fatoum
2024-12-19 17:47 ` Frank Li
2024-12-19 17:51 ` Ahmad Fatoum
2024-12-19 19:16 ` Frank Li
2024-12-20 9:12 ` Ahmad Fatoum
2024-12-20 15:38 ` Frank Li
2025-01-06 15:59 ` Ahmad Fatoum
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=Z2RzoITPUmZFoX09@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=a.fatoum@pengutronix.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox