From: Bjorn Andersson <andersson@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@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,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
Subject: Re: [PATCH 2/3] arm64: dts: qcom: glymur: Add Asus Zenbook A14 (UX3407NA)
Date: Sun, 28 Jun 2026 20:04:50 -0500 [thread overview]
Message-ID: <akHEKifRtKksIbpQ@baldur> (raw)
In-Reply-To: <obf2iw3wq6xuvftkkwf4wa47i4y7q2apoaa5a5vvprrcqphawo@gr2snc33hnph>
On Sun, Jun 28, 2026 at 04:20:22PM +0300, Dmitry Baryshkov wrote:
> On Sat, Jun 27, 2026 at 09:41:38PM -0500, Bjorn Andersson wrote:
> > On Tue, Jun 23, 2026 at 09:06:51AM +0200, Konrad Dybcio wrote:
> > > On 6/23/26 3:31 AM, Bjorn Andersson wrote:
> > > > From: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> > > >
> > > > UX3407NA is a variant of the Asus Zenbook A14 built on the Qualcomm
> > > > Glymur platform. It comes with an 18-core X2 Elite SoC, 32GB DDR, and
> > > > the other typical Glymur platform capabilities.
> > > >
> > > > The Asus Zenbook uses &pcie3b for NVMe storage, the screen is WUXGA
> > > > OLED, it has two USB Type-C ports, one USB Type-A, and one HDMI port.
> > > >
> > > > Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> > > > ---
> > > > +&tlmm {
> > > > + gpio-reserved-ranges = <4 4>, /* EC Secure */
> > > > + <10 2>, /* OOB UART */
> > > > + <44 4>, /* TPM */
> > > > + <90 2>; /* TPM */
> > >
> > > Is there no EC reset pin? I wouldn't want others to have to open up
> > > a laptop after trying to find out what it does..
>
> :-)
>
> > >
> >
> > These are the ones needed to allow the thing to boot, I don't know what
> > the EC reset pin does, but I guess we can add some more for convenience.
> >
> > [..]
> > > > +&uart21 {
> > > > + status = "disabled";
> > >
> > > hm?
> > >
> >
> > The debug-uart is left enabled in glymur.dtsi. Perhaps we should change
> > that instead?
>
> I think that would match other platforms. But, is it actually not wired
> up? No debug connector or TPs?
>
It might very well be, but like most other users I don't intend to ever
use them...
Regards,
Bjorn
> --
> With best wishes
> Dmitry
next prev parent reply other threads:[~2026-06-29 1:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 1:31 [PATCH 0/3] arm64: dts: qcom: Introduce Asus Zenbook A14 (UX3407NA) Bjorn Andersson
2026-06-23 1:31 ` [PATCH 1/3] dt-bindings: arm: qcom: Add " Bjorn Andersson
2026-06-23 7:12 ` Krzysztof Kozlowski
2026-06-23 1:31 ` [PATCH 2/3] arm64: dts: qcom: glymur: " Bjorn Andersson
2026-06-23 7:06 ` Konrad Dybcio
2026-06-28 2:41 ` Bjorn Andersson
2026-06-28 13:20 ` Dmitry Baryshkov
2026-06-29 1:04 ` Bjorn Andersson [this message]
2026-06-23 1:31 ` [PATCH 3/3] firmware: qcom: scm: Allow QSEECOM on " Bjorn Andersson
2026-06-28 13:20 ` Dmitry Baryshkov
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=akHEKifRtKksIbpQ@baldur \
--to=andersson@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox