From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Konstantin Shabanov <mail@etehtsea.me>
Cc: andersson@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] arm64: dts: qcom: Add HONOR MagicBook Art 14 device tree
Date: Wed, 24 Jun 2026 14:10:29 +0200 [thread overview]
Message-ID: <34408f18-0d1b-4828-a0ce-feb54f536ef2@oss.qualcomm.com> (raw)
In-Reply-To: <20260620173833.17728-1-mail@etehtsea.me>
On 6/20/26 7:38 PM, Konstantin Shabanov wrote:
> On Tue, 16 Jun 2026 14:37:13 +0200 Konrad Dybcio wrote:
>>> +/* MP0 goes to the USB-A port(USB3) and FPC */
>>
>> "MP0" refers to the first USB3+USB2 port on the multiport controller.
>> Is there a hub inbetween? Should we describe it? Do we know if VBUS on
>> the USB-A port is controllable?
>
> Unfortunately, I couldn't find any documentation for this laptop, and
> all I can tell is that the USB-A port seems to work and the FPC is
> recognized:
>
> Bus 005 Device 002: ID 10a5:9924 FPC FPC L:2407 FW:3334147
OK, if it works, it works
Konrad
next prev parent reply other threads:[~2026-06-24 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 17:29 [PATCH v2 0/4] Introduce " Konstantin Shabanov
2026-05-15 17:29 ` [PATCH v2 1/4] dt-bindings: vendor-prefixes: Add HONOR Konstantin Shabanov
2026-05-15 17:29 ` [PATCH v2 2/4] dt-bindings: arm: qcom: Add HONOR MagicBook Art 14 Konstantin Shabanov
2026-05-15 17:29 ` [PATCH v2 3/4] arm64: dts: qcom: Add HONOR MagicBook Art 14 device tree Konstantin Shabanov
2026-06-16 12:37 ` Konrad Dybcio
2026-06-20 17:38 ` Konstantin Shabanov
2026-06-24 12:10 ` Konrad Dybcio [this message]
2026-05-15 17:29 ` [PATCH v2 4/4] firmware: qcom: scm: Allow QSEECOM on Honor Magicbook Art 14 Konstantin Shabanov
2026-05-17 18:27 ` Dmitry Baryshkov
2026-06-23 18:27 ` [PATCH v2 0/4] Introduce HONOR MagicBook Art 14 device tree Valentin Manea
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=34408f18-0d1b-4828-a0ce-feb54f536ef2@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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®