From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Konstantin Shabanov <mail@etehtsea.me>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/4] arm64: dts: qcom: Add HONOR MagicBook Art 14 device tree
Date: Wed, 24 Jun 2026 14:07:16 +0200 [thread overview]
Message-ID: <5b3559ba-7c69-4418-a0a4-c5fa614830c4@oss.qualcomm.com> (raw)
In-Reply-To: <20260620175210.19563-4-mail@etehtsea.me>
On 6/20/26 7:51 PM, Konstantin Shabanov wrote:
> Introduce support for the HONOR MagicBook Art 14 laptop.
> This version is based on the initial work by Kirill A. Korinsky [1]
> and Valentin Manea [2].
[...]
> +/* MP0 goes to the USB-A port(USB3) and FPC */
> +&usb_mp {
> + /* Limit to single port */
> + phys = <&usb_mp_hsphy0>, <&usb_mp_qmpphy0>;
> + phy-names = "usb2-0", "usb3-0";
> +
> + status = "okay";
> +};
It's fine to keep the other one enabled, if only to make sure that
it's powered off sanely
Konrad
next prev parent reply other threads:[~2026-06-24 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 17:51 [PATCH v3 0/4] Introduce HONOR MagicBook Art 14 Snapdragon " Konstantin Shabanov
2026-06-20 17:51 ` [PATCH v3 1/4] dt-bindings: vendor-prefixes: Add HONOR Konstantin Shabanov
2026-06-20 17:51 ` [PATCH v3 2/4] dt-bindings: arm: qcom: Add HONOR MagicBook Art 14 Konstantin Shabanov
2026-06-20 17:51 ` [PATCH v3 3/4] arm64: dts: qcom: Add HONOR MagicBook Art 14 device tree Konstantin Shabanov
2026-06-24 12:07 ` Konrad Dybcio [this message]
2026-06-24 12:10 ` Konrad Dybcio
2026-06-28 8:20 ` [PATCH v3 0/4] Introduce HONOR MagicBook Art 14 Snapdragon " Konstantin Shabanov
2026-06-29 9:28 ` Konrad Dybcio
2026-06-20 17:51 ` [PATCH v3 4/4] firmware: qcom: scm: Allow QSEECOM on Honor Magicbook Art 14 Konstantin Shabanov
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=5b3559ba-7c69-4418-a0a4-c5fa614830c4@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=mail@etehtsea.me \
--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®