From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Umang Chheda <umang.chheda@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, 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,
mohd.anwar@oss.qualcomm.com, krishna.chundru@oss.qualcomm.com,
monish.chunara@oss.qualcomm.com
Subject: Re: [PATCH v2 1/1] arm64: dts: qcom: monaco-evk: Add Interface Plus Mezzanine
Date: Mon, 23 Feb 2026 13:48:18 +0100 [thread overview]
Message-ID: <43c62c23-e75d-425c-b788-050101719d70@oss.qualcomm.com> (raw)
In-Reply-To: <6d9b9e85-5a54-461d-8f34-daf0c042b2b4@oss.qualcomm.com>
On 2/23/26 11:36 AM, Umang Chheda wrote:
>
> On 2/23/2026 3:29 PM, Konrad Dybcio wrote:
>> On 2/23/26 10:47 AM, Umang Chheda wrote:
>>> Hello Dmitry,
>>>
>>> On 2/22/2026 11:57 PM, Dmitry Baryshkov wrote:
>>>> On Sun, Feb 22, 2026 at 11:05:45PM +0530, Umang Chheda wrote:
>>>>> The Interface Plus [IFP] Mezzanine is an hardware expansion add-on
>>>>> board designed to be stacked on top of Monaco EVK.
>>>>>
>>>>> It has following peripherals :
>>>>>
>>>>> - 4x Type A USB ports in host mode.
>>>>> - TC9563 PCIe switch, which has following three downstream ports (DSP) :
>>>>> - 1st DSP connects M.2 E-key connector for connecting WLAN endpoints.
>>>> Nit: routed to? Is that M.2 only suitable for WLANs? What is "WLAN
>>>> endpoints"?
>>>> routed to?
>>> If I understand correctly - you mean change string "connects M.2 E-Key connector" to
>>> "routed to M.2 E-Key connector" ?
>>>
>>>
>>>> Is that M.2 only suitable for WLANs?
>>> Yes, this is suitable only for the WLAN module.
>> If I remove that WLAN module and insert an SSD through an adapter, will
>> the board spontaneously explode?
>>
>> "intended for" is less ominous..
>
>
> Hmm Yes I agree -- will re-phrase the above statement to something like below :
>
> "The first downstream port (DSP) is routed to an M.2 E‑Key connector, intended for WLAN modules.”
Sounds good, thanks!
Konrad
next prev parent reply other threads:[~2026-02-23 12:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 17:35 [PATCH v2 0/1] Introduce Monaco EVK Interface Plus Mezzanine Umang Chheda
2026-02-22 17:35 ` [PATCH v2 1/1] arm64: dts: qcom: monaco-evk: Add " Umang Chheda
2026-02-22 18:27 ` Dmitry Baryshkov
2026-02-23 9:47 ` Umang Chheda
2026-02-23 9:59 ` Konrad Dybcio
2026-02-23 10:36 ` Umang Chheda
2026-02-23 12:48 ` Konrad Dybcio [this message]
2026-02-23 18:56 ` Dmitry Baryshkov
2026-02-27 7:23 ` Umang Chheda
2026-02-23 13:12 ` Krzysztof Kozlowski
2026-02-23 15:12 ` Bjorn Andersson
2026-02-23 15:36 ` Krzysztof Kozlowski
2026-02-23 19:02 ` Dmitry Baryshkov
2026-02-23 20:37 ` Krzysztof Kozlowski
2026-02-23 22:09 ` Dmitry Baryshkov
2026-02-27 9:50 ` Umang Chheda
2026-02-27 10:38 ` Krzysztof Kozlowski
2026-02-24 4:29 ` Bjorn Andersson
2026-02-24 6:55 ` Krzysztof Kozlowski
2026-02-27 9:46 ` Umang Chheda
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=43c62c23-e75d-425c-b788-050101719d70@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohd.anwar@oss.qualcomm.com \
--cc=monish.chunara@oss.qualcomm.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=umang.chheda@oss.qualcomm.com \
/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