From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mecid Urganci <mecid@mecomediagroup.de>,
andersson@kernel.org, konradybcio@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
richardcochran@gmail.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: Add qcs9075-radxa-airbox-q900
Date: Wed, 18 Mar 2026 11:10:56 +0100 [thread overview]
Message-ID: <6e32e5ac-bdc4-4745-b819-0f409a6f6891@oss.qualcomm.com> (raw)
In-Reply-To: <20260318083621.470826-3-mecid@mecomediagroup.de>
On 3/18/26 9:36 AM, Mecid Urganci wrote:
> Add device tree support for the Radxa AirBox Q900 board based on the
> Qualcomm QCS9075 SoC (Lemans Family).
>
> This board features HDMI 2.0 via dp0, 2x USB 3.1 Gen 2 ports,
> 2x 2.5GbE Ethernet ports and onboard UFS storage.
>
> Further information: https://radxa.com/products/fogwise/airbox-q900/
>
> Functionality has been tested and confirmed working via an Armbian
> Debian Trixie build.
>
> Signed-off-by: Mecid Urganci <mecid@mecomediagroup.de>
> Made-with: Cursor
> ---
[...]
> + gpio_leds: gpio-leds {
Please strip unused labels
> + compatible = "gpio-leds";
> + pinctrl-names = "default";
> + pinctrl-0 = <&status_led_state>, <&power_led_state>;
property-n
property-names
in this order, file-wide, please
[...]
> + vreg_l4c: ldo4 {
> + regulator-name = "vreg_l4c";
> + regulator-min-microvolt = <1200000>;
> + regulator-max-microvolt = <1200000>;
> + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> + /*
> + * FIXME: This should have regulator-allow-set-load but
> + * we're getting an over-current fault from the PMIC
> + * when switching to LPM.
> + */
Are you actually experiencing that, or is that a copy-pasta?
[...]
> +&i2c15 {
> + clock-frequency = <400000>;
> + status = "okay";
Please uniformly keep a \n before 'status'
[...]
> +&gpu_zap_shader {
> + firmware-name = "qcom/sa8775p/a663_zap.mbn";
> +};
> +
> +&iris {
> + firmware-name = "qcom/vpu/vpu30_p4_s6.mbn";
> + status = "okay";
> +};
Those are only Qualcomm-signed (i.e. not vendor-signed) - are you
using the ones from linux-firmware?
[...]
> +&remoteproc_adsp {
> + firmware-name = "qcom/sa8775p/adsp.mbn";
Notably the ADSP firmware normally contains board-specific modifications..
[...]
> + power_led_state: power-led-state {
> + pins = "gpio98";
> + function = "gpio";
> + output-high;
You're already manipulating this pin from the gpio-leds node, no need
> + bias-pull-up;
pull-up of an active-high pin sounds odd
Konrad
prev parent reply other threads:[~2026-03-18 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 8:36 [PATCH 0/2] arm64: dts: qcom: Add support for Radxa AirBox Q900 Mecid Urganci
2026-03-18 8:36 ` [PATCH 1/2] dt-bindings: arm: qcom: Add qcs9075-radxa-airbox-q900 Mecid Urganci
2026-03-18 8:51 ` Krzysztof Kozlowski
2026-03-18 9:55 ` mecid
2026-03-18 10:15 ` Krzysztof Kozlowski
2026-03-18 8:36 ` [PATCH 2/2] arm64: dts: " Mecid Urganci
2026-03-18 8:56 ` Krzysztof Kozlowski
2026-03-18 10:02 ` mecid
2026-03-18 8:57 ` Neil Armstrong
2026-03-18 10:10 ` Konrad Dybcio [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=6e32e5ac-bdc4-4745-b819-0f409a6f6891@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mecid@mecomediagroup.de \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
/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®