From: sashiko-bot@kernel.org
To: "Alexandre MINETTE via B4 Relay"
<devnull+contact.alex-min.fr@kernel.org>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 8/8] ARM: dts: qcom: Add Samsung Galaxy S4
Date: Tue, 19 May 2026 09:50:42 +0000 [thread overview]
Message-ID: <20260519095042.B71A1C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519-mainline-send-v1-sending-v3-8-3dd7aa125353@alex-min.fr>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The 'sda-gpios' and 'scl-gpios' properties in the 'i2c-muic' node omit the 'GPIO_OPEN_DRAIN' flag.
--
commit 2dc0aa912f65c9935abe21e36b8281387360daac
Author: Alexandre MINETTE <contact@alex-min.fr>
ARM: dts: qcom: Add Samsung Galaxy S4
This commit adds a device tree for the Samsung Galaxy S4 (jflte) based on the
Qualcomm APQ8064 platform. It includes initial support for UART, USB peripheral
mode, LEDs, and physical buttons.
> diff --git a/arch/arm/boot/dts/qcom/qcom-apq8064-samsung-jflte.dts b/arch/arm/boot/dts/qcom/qcom-apq8064-samsung-jflte.dts
> new file mode 100644
> index 0000000000000..2f10466077c7a
> --- /dev/null
> +++ b/arch/arm/boot/dts/qcom/qcom-apq8064-samsung-jflte.dts
[ ... ]
> + i2c-muic {
> + compatible = "i2c-gpio";
> + sda-gpios = <&tlmm_pinmux 22 GPIO_ACTIVE_HIGH>;
> + scl-gpios = <&tlmm_pinmux 23 GPIO_ACTIVE_HIGH>;
Does this configuration omit the GPIO_OPEN_DRAIN flag?
The i2c-gpio driver requests the pins with GPIOD_OUT_HIGH_OPEN_DRAIN.
When the GPIO_OPEN_DRAIN flag is omitted in the device tree, the GPIO
subsystem enforces the open-drain semantics to prevent hardware issues
but emits a boot warning about the missing flag.
Could the GPIO_OPEN_DRAIN flag be added here to satisfy the i2c-gpio
bindings and silence the warning, similar to how the i2c-led node is
configured?
> + i2c-gpio,delay-us = <2>;
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260519-mainline-send-v1-sending-v3-0-3dd7aa125353@alex-min.fr?part=8
next prev parent reply other threads:[~2026-05-19 9:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 7:16 [PATCH v3 0/8] Add Samsung Galaxy S4 support Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 7:16 ` [PATCH v3 1/8] dt-bindings: arm: qcom: Add Samsung Galaxy S4 Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 7:16 ` [PATCH v3 2/8] dt-bindings: extcon: qcom,pm8941-misc: Add PM8921 compatible Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 7:42 ` sashiko-bot
2026-05-20 7:22 ` Krzysztof Kozlowski
2026-06-03 9:16 ` MINETTE Alexandre
2026-05-19 7:16 ` [PATCH v3 3/8] pinctrl: qcom: Register functions before enabling pinctrl Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 8:12 ` sashiko-bot
2026-05-19 8:31 ` Linus Walleij
2026-05-19 8:48 ` MINETTE Alexandre
2026-05-19 21:03 ` David Heidelberg
2026-06-03 8:58 ` MINETTE Alexandre
2026-06-03 12:29 ` Dmitry Baryshkov
2026-06-03 12:44 ` MINETTE Alexandre
2026-05-19 7:16 ` [PATCH v3 4/8] iommu/msm: Look up masters per IOMMU instance Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 8:43 ` sashiko-bot
2026-05-19 7:16 ` [PATCH v3 5/8] extcon: qcom-spmi-misc: Add PM8921 compatible Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 9:05 ` sashiko-bot
2026-05-19 7:16 ` [PATCH v3 6/8] ARM: dts: qcom: apq8064: Fix USB controller clocks Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 9:25 ` sashiko-bot
2026-05-19 7:16 ` [PATCH v3 7/8] ARM: dts: qcom: pm8921: Add USB ID extcon Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 9:41 ` sashiko-bot
2026-05-19 7:16 ` [PATCH v3 8/8] ARM: dts: qcom: Add Samsung Galaxy S4 Alexandre MINETTE via B4 Relay
2026-05-19 7:16 ` Alexandre MINETTE
2026-05-19 9:50 ` sashiko-bot [this message]
2026-05-25 9:01 ` Linus Walleij
2026-05-21 10:41 ` Konrad Dybcio
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=20260519095042.B71A1C2BCB3@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+contact.alex-min.fr@kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.