Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Kaustabh Chakraborty" <kauschluss@disroot.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 3/3] arm64: dts: exynos7870-j6lte: add Sharp GP2AP070S proximity sensor
Date: Thu, 30 Jul 2026 20:19:11 +0000	[thread overview]
Message-ID: <20260730201911.F3A9C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260731-gp2ap070s-v3-3-d1f5cecf9fe7@disroot.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `i2c_proxm_bus` pinctrl node assigns a hardware alternate pin function (`EXYNOS_PIN_FUNC_3`) to pins that are driven by a software bit-banged `i2c-gpio` device.
--

--- Patch [3]: [PATCH v3 3/3] arm64: dts: exynos7870-j6lte: add Sharp GP2AP070S proximity sensor ---
commit 2279f9b3f632fe5641c2ffa9eb9b410688448a06
Author: Kaustabh Chakraborty <kauschluss@disroot.org>

arm64: dts: exynos7870-j6lte: add Sharp GP2AP070S proximity sensor

This commit adds the devicetree node for the Sharp GP2AP070S proximity sensor
which is connected to a GPIO-driven I2C line, alongside a new fixed regulator
for its VDD supply.

> diff --git a/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts b/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts
> index de30d0970336f..dd493138fed6e 100644
> --- a/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts
> +++ b/arch/arm64/boot/dts/exynos/exynos7870-j6lte.dts
> @@ -73,6 +73,35 @@ key-volup {
>  		};
>  	};
>  
> +	i2c-proximity {
> +		compatible = "i2c-gpio";
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&i2c_proxm_bus>;
> +
> +		sda-gpios = <&gpf4 3 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> +		scl-gpios = <&gpf4 2 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;

[ ... ]

> @@ -579,6 +624,12 @@ bt_enable: bt-enable-pins {
>  		samsung,pin-pud = <EXYNOS_PIN_PULL_DOWN>;
>  	};
>  

[Severity: Medium]
Is it intentional to configure a hardware alternate function for a bus that
is driven by a software i2c-gpio device?

The i2c-proximity node uses the i2c-gpio driver for software bit-banging, but
the i2c_proxm_bus pinctrl configuration below assigns EXYNOS_PIN_FUNC_3 instead
of a standard GPIO function.

This configuration can cause the pinctrl framework to briefly connect the pins
to a hardware IP block before the GPIO framework requests them and forces them
back to software mode. If the underlying hardware IP is active during this
initialization window, it could drive the lines and lead to transient bus
contention or glitches on the sensor during system probe.

> +	i2c_proxm_bus: i2c-proxm-bus-pins {
> +		samsung,pins = "gpf4-3", "gpf4-2";
> +		samsung,pin-function = <EXYNOS_PIN_FUNC_3>;
> +		samsung,pin-pud = <EXYNOS_PIN_PULL_NONE>;
> +	};
> +

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260731-gp2ap070s-v3-0-d1f5cecf9fe7@disroot.org?part=3

      reply	other threads:[~2026-07-30 20:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 20:06 [PATCH v3 0/3] Add Sharp GP2AP070S Proximity Driver and enable it in Galaxy J6 (j6lte) Kaustabh Chakraborty
2026-07-30 20:07 ` [PATCH v3 1/3] dt-bindings: iio: proximity: add Sharp GP2AP070S proximity sensor Kaustabh Chakraborty
2026-07-30 20:12   ` sashiko-bot
2026-07-30 20:07 ` [PATCH v3 2/3] iio: proximity: add driver for " Kaustabh Chakraborty
2026-07-30 20:18   ` sashiko-bot
2026-07-30 20:07 ` [PATCH v3 3/3] arm64: dts: exynos7870-j6lte: add " Kaustabh Chakraborty
2026-07-30 20:19   ` sashiko-bot [this message]

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=20260730201911.F3A9C1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kauschluss@disroot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox