All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Abel Vesa <abel.vesa@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/3] arm64: dts: qcom: glymur: Add ASUS Ascent QN10
Date: Tue, 17 Nov 2026 15:41:05 +0000	[thread overview]
Message-ID: <86eccj1n5a.wl-maz@kernel.org> (raw)
In-Reply-To: <20261115-qn10-v2-0-19b11603e776@oss.qualcomm.com>

On Mon, 16 Nov 2026 03:48:58 +0000,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com> wrote:
> 
> Introduce the ASUS Ascent QN10 compact desktop computer.
> 
> Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> ---
> Changes in v2:
> - Move the RPMH regulator override below the SOCCP remoteproc node.
> - Sort the GMU and GPU node overrides by label.
> - Drop the unused EC interrupt pinctrl state.
> - Link to v1: https://patch.msgid.link/20261113-qn10-v1-0-e09b2aa7ccbe@oss.qualcomm.com
> 
> ---
> Bjorn Andersson (3):
>       dt-bindings: arm: qcom: Add ASUS Ascent QN10
>       arm64: dts: qcom: glymur: Add ASUS Ascent QN10
>       firmware: qcom: Allow QSEECOM on ASUS Ascent QN10
> 
>  Documentation/devicetree/bindings/arm/qcom.yaml    |   1 +
>  arch/arm64/boot/dts/qcom/Makefile                  |   1 +
>  .../boot/dts/qcom/glymur-asus-ascent-qn10.dts      | 664 +++++++++++++++++++++
>  drivers/firmware/qcom/qcom_scm.c                   |   1 +
>  4 files changed, 667 insertions(+)

I've thrown this DT at the Ubuntu installer, and ended up with a (more
or less) working machine, so something here must be good!

I get a 2-minute timeout in EFI services though, something that mostly
speak to the quality of the firmware rather than the HW description,
and is worked around with an 'efi=noruntime' on the command-line.

Now off to locate the UART on the debug connector...

FWIW:

Tested-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Without deviation from the norm, progress is not possible.

      parent reply	other threads:[~2026-11-17 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  3:48 [PATCH v2 0/3] arm64: dts: qcom: glymur: Add ASUS Ascent QN10 Bjorn Andersson
2026-11-16  3:48 ` [PATCH v2 1/3] dt-bindings: arm: qcom: " Bjorn Andersson
2026-11-16  3:49 ` [PATCH v2 2/3] arm64: dts: qcom: glymur: " Bjorn Andersson
2026-11-16  5:53   ` Val Packett
2026-11-16  3:49 ` [PATCH v2 3/3] firmware: qcom: Allow QSEECOM on " Bjorn Andersson
2026-11-17  1:45 ` (subset) [PATCH v2 0/3] arm64: dts: qcom: glymur: Add " Bjorn Andersson
2026-11-17  3:19 ` Bjorn Andersson
2026-11-17 15:41 ` Marc Zyngier [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=86eccj1n5a.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.