From: Marek Vasut <marex@nabladev.com>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
robh@kernel.org, Frank.Li@kernel.org, imx@lists.linux.dev,
conor+dt@kernel.org, Oliver Hartkopp <socketcan@hartkopp.net>,
Oleksij Rempel <o.rempel@pengutronix.de>,
linux-can@vger.kernel.org, Vincent Mailhol <mailhol@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 3/3] arm64: dts: imx95: Add support for Data Modul i.MX95 eDM SBC
Date: Thu, 17 Sep 2026 20:55:56 +0200 [thread overview]
Message-ID: <c1197d8e-add5-48b7-b0ba-a5a91379ab04@nabladev.com> (raw)
In-Reply-To: <aqw1agBrSjYoy71_@SMW015318>
On 9/17/26 8:46 PM, Frank Li wrote:
Hello Frank,
[...]
>>>>> + reg_panel_vcc: regulator-panel-vcc {
>>>>> + compatible = "regulator-fixed";
>>>>> + regulator-min-microvolt = <3300000>;
>>>>> + regulator-max-microvolt = <3300000>;
>>>>> + regulator-name = "PANEL_VCC";
>>>>> + gpios = <&i2c2_gpio_expander_20 17 0>;
>>>
>>> gpio third arg 0, means GPIO_ACTIVE_HIGH
>>>
>>> so need enable-active-high
>>>
>>> if your boards have invertor should use GPIO_ACTIVE_LOW
>>
>> I already went through all that, please see "Re: [PATCH 3/3] arm64: dts:
>> imx95: Add support for Data Modul i.MX95 eDM SBC" .
>
> at https://lore.kernel.org/imx/f4dbeaac-ab10-4980-9fc5-533907be223c@nabladev.com/
>
> <&i2c2_gpio_expander_20 17 0>;
> ^
>
> 0 should use predefine MACRO, after I check 0 means GPIO_ACTIVE_HIGH.
>
> so need enable-active-high for regulator.
This is extended via a DTO, so no, I must not use a macro because I do
not know the polarity of this signal, that is why there is 0 here.
The enable-active-high DT property must explicitly NOT be here, because
the DTO can not remove properties from the base DT. Adding
enable-active-high here would make the DTO unable to operate this signal
as active-low .
>>>>> + tas2552: audio-codec@40 {
>>>>> + compatible = "ti,tas2552";
>>>>> + reg = <0x40>;
>>>>> + #sound-dai-cells = <0>;
>>>>> + avdd-supply = <®_1p8v>;
>>>>> + iovdd-supply = <®_3p3v>;
>>>>> + vbat-supply = <®_5p0v>;
>>>>> + enable-gpio = <&i2c2_gpio_expander_20 23 GPIO_ACTIVE_HIGH>;
>>>>
>>>> [Severity: Low]
>>>> This isn't a bug, but should tas2552 be using the enable-gpios property name
>>>> instead of the deprecated enable-gpio? The patch changelog mentions replacing
>>>> gpio with gpios DT properties.
>>>
>>> Please fix this one.
>>
>> No, this is correct, see
>>
>> Documentation/devicetree/bindings/sound/ti,tas2552.yaml: enable-gpio:
>
> It is fine now, I suggest update bindings to allow both. which convert
> by Rob at Jan 2026. I think Rob may miss it.
>
> kernel hack code covert -gpio to -gpios
I'll add that into my todo, but that is a separate fix from this DT.
next prev parent reply other threads:[~2026-09-17 23:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 6:25 [PATCH v4 1/3] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6563 Marek Vasut
2026-09-17 6:25 ` [PATCH v4 2/3] dt-bindings: arm: fsl: Document Data Modul i.MX95 eDM SBC Marek Vasut
2026-09-18 11:01 ` Krzysztof Kozlowski
2026-09-17 6:25 ` [PATCH v4 3/3] arm64: dts: imx95: Add support for " Marek Vasut
2026-09-17 6:35 ` sashiko-bot
2026-09-17 16:53 ` Frank Li
2026-09-17 17:19 ` Marek Vasut
2026-09-17 18:46 ` Frank Li
2026-09-17 18:55 ` Marek Vasut [this message]
2026-09-18 13:58 ` Frank Li
2026-09-20 17:05 ` Marek Vasut
2026-09-21 16:24 ` Frank Li
2026-09-21 16:37 ` Marek Vasut
2026-09-21 17:11 ` Frank Li
2026-09-21 18:43 ` Marek Vasut
2026-09-21 19:23 ` Frank Li
2026-09-21 21:46 ` Marek Vasut
2026-09-17 6:31 ` [PATCH v4 1/3] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6563 sashiko-bot
2026-09-18 10:58 ` Krzysztof Kozlowski
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=c1197d8e-add5-48b7-b0ba-a5a91379ab04@nabladev.com \
--to=marex@nabladev.com \
--cc=Frank.Li@kernel.org \
--cc=Frank.li@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-can@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=socketcan@hartkopp.net \
/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