From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Umang Chheda <umang.chheda@oss.qualcomm.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
richardcochran@gmail.com
Cc: 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 1/1] arm64: dts: qcom: monaco-evk: Add Mezzanine
Date: Thu, 12 Feb 2026 14:40:02 +0100 [thread overview]
Message-ID: <957d7896-cd01-4864-bf07-e6dbdfff1273@oss.qualcomm.com> (raw)
In-Reply-To: <20260210103821.4169-2-umang.chheda@oss.qualcomm.com>
On 2/10/26 11:38 AM, Umang Chheda wrote:
> The Mezzanine is an hardware expansion add-on board designed
There's normally multiple mezzanine boards (e.g. a "vision mezzanine"),
is there a better name for it?
[...]
> +&tlmm {
> + tc9563_resx_n: tc9563-resx-state {
> + pins = "gpio124";
> + function = "gpio";
> +
> + bias-disable;
please drop the empty line above
Konrad
next prev parent reply other threads:[~2026-02-12 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 10:38 [PATCH 0/1] Introduce Monaco EVK Peripheral Mezzanine Umang Chheda
2026-02-10 10:38 ` [PATCH 1/1] arm64: dts: qcom: monaco-evk: Add Mezzanine Umang Chheda
2026-02-10 12:30 ` Dmitry Baryshkov
2026-02-12 13:40 ` Konrad Dybcio [this message]
2026-02-12 15:50 ` Umang Chheda
2026-02-12 16:29 ` Konrad Dybcio
2026-02-16 8:04 ` Umang Chheda
2026-02-16 11:14 ` Konrad Dybcio
2026-02-17 6:43 ` Umang Chheda
2026-02-17 9:40 ` Konrad Dybcio
2026-02-17 14:52 ` Umang Chheda
2026-02-12 20:03 ` Bjorn Andersson
2026-02-16 8:14 ` Umang Chheda
2026-02-17 20:56 ` Bjorn Andersson
2026-02-20 7:07 ` Umang Chheda
2026-02-10 12:29 ` [PATCH 0/1] Introduce Monaco EVK Peripheral Mezzanine 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=957d7896-cd01-4864-bf07-e6dbdfff1273@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=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