mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Hui <bg9oxa@163.com>
To: Shawn Lin <shawn.lin@rock-chips.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	sashiko-bot <sashiko-bot@kernel.org>
Subject: Re: [PATCH v8 2/2] arm64: dts: rockchip: Add ALIENTEK QuarkPi-CA2
Date: Tue, 13 Oct 2026 04:00:59 +0800	[thread overview]
Message-ID: <179183525969.9903.16050666483943242352@163.com> (raw)
In-Reply-To: <9a8c6a76-8972-4b1e-8384-842668621fce@rock-chips.com>

Hi Shawn,

Thanks for the review.

The 3.3 V rail of the M.2 E-key socket (VCC3V3_PCIE) is not a PMIC output:
it is generated by its own buck on the M.2/WiFi sheet (U36, SY8089AAC),
fed from the board input rail, and its EN pin is tied high through R246
(10k), with the 100 nF capacitor on that pin (C477) not populated. There
is no GPIO for it, so Linux cannot gate the rail.

That is why it carries always-on/boot-on - to state that the rail is not
switchable. Boards where the M.2 3.3 V rail has an enable GPIO, like
rk3568-rock-3a, omit them; for a fixed rail this pair is the usual
description, as in rk3566-soquartz-model-a.dts.

If you would rather the rail was not described at all, I can drop the node
and the vpcie3v3-supply reference; the hardware is the same either way.

Thanks,
Bob


      reply	other threads:[~2026-10-12 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07  5:18 [PATCH v8 0/2] " Bob Hui
2026-10-07  5:18 ` [PATCH v8 1/2] dt-bindings: arm: " Bob Hui
2026-10-07  9:52   ` Conor Dooley
2026-10-07  5:18 ` [PATCH v8 2/2] arm64: dts: " Bob Hui
     [not found]   ` <sashiko-outbox-162642@kernel.org>
2026-10-07  6:24     ` Bob Hui
2026-10-11  3:31   ` Shawn Lin
2026-10-12 20:00     ` Bob Hui [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=179183525969.9903.16050666483943242352@163.com \
    --to=bg9oxa@163.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=sashiko-bot@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    /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

all inboxes | Powered by JetHome®