All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Daniel Palmer" <daniel@thingy.jp>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 2/8] ARM: dts: mstar: unitv2: Add regulators
Date: Mon, 13 Jul 2026 11:08:37 +0000	[thread overview]
Message-ID: <20260713110838.295471F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260713105950.1346962-3-daniel@thingy.jp>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing `enable-active-high` property in `reg_vcc_wifi` causes the gpiolib core to forcefully invert its GPIO polarity to active-low.
--

--- Patch [2]: [PATCH 2/8] ARM: dts: mstar: unitv2: Add regulators ---
commit 45b1e50aa0d58e3444d010d9375cea0bd438d0d9
Author: Daniel Palmer <daniel@0x0f.com>
ARM: dts: mstar: unitv2: Add regulators

This commit adds fixed regulators for the core, IO, and DRAM voltage rails.
It also introduces a GPIO-controlled switch that supplies the WiFi chip.

> diff --git a/arch/arm/boot/dts/sigmastar/mstar-infinity2m-ssd202d-unitv2.dts b/arch/arm/boot/dts/sigmastar/mstar-infinity2m-ssd202d-unitv2.dts
> --- a/arch/arm/boot/dts/sigmastar/mstar-infinity2m-ssd202d-unitv2.dts
> +++ b/arch/arm/boot/dts/sigmastar/mstar-infinity2m-ssd202d-unitv2.dts
[ ... ]
> +	reg_vcc_wifi: regulator-vcc-wifi {
> +		compatible = "regulator-fixed";
> +		regulator-name = "vcc_wifi";
> +		regulator-min-microvolt = <3300000>;
> +		regulator-max-microvolt = <3300000>;
> +		gpio = <&gpio SSD20XD_GPIO_GPIO14 GPIO_ACTIVE_HIGH>;

[Severity: Medium]
Will the gpiolib core force this GPIO to active-low polarity?

Due to a legacy quirk for regulator-fixed nodes in the gpiolib core, the
GPIO_ACTIVE_HIGH flag in the phandle is ignored in favor of the boolean
enable-active-high property. Without the enable-active-high property present
here, will the WiFi chip receive inverted power control and fail to operate?

> +	};
>  };
[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260713105950.1346962-1-daniel@thingy.jp?part=2

  reply	other threads:[~2026-07-13 11:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 10:59 [PATCH 0/8] ARM: mstar: Board filling out pt. 1 Daniel Palmer
2026-07-13 10:59 ` [PATCH 1/8] ARM: dts: mstar: unitv2: Wire up LEDs Daniel Palmer
2026-07-13 10:59 ` [PATCH 2/8] ARM: dts: mstar: unitv2: Add regulators Daniel Palmer
2026-07-13 11:08   ` sashiko-bot [this message]
2026-07-13 10:59 ` [PATCH 3/8] ARM: dts: mstar: unitv2: Add button Daniel Palmer
2026-07-13 10:59 ` [PATCH 4/8] ARM: dts: mstar: unitv2: Link cpu to core regulator Daniel Palmer
2026-07-13 11:07   ` sashiko-bot
2026-07-13 10:59 ` [PATCH 5/8] ARM: dts: mstar: miyoo-mini: Add vibrator Daniel Palmer
2026-07-13 11:08   ` sashiko-bot
2026-07-13 10:59 ` [PATCH 6/8] ARM: dts: mstar: miyoo-mini: Add vbat switch Daniel Palmer
2026-07-13 11:09   ` sashiko-bot
2026-07-13 10:59 ` [PATCH 7/8] ARM: dts: mstar: sbc2d06: Add regulators Daniel Palmer
2026-07-13 11:08   ` sashiko-bot
2026-07-13 10:59 ` [PATCH 8/8] ARM: dts: mstar: ssd201htv2: Add SD card supply regulator Daniel Palmer
2026-07-13 11:11   ` sashiko-bot

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=20260713110838.295471F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=daniel@thingy.jp \
    --cc=devicetree@vger.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.