public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v4 1/4] arm64: dts: qcom: monaco-evk: Extract common EVK hardware into shared dtsi
Date: Mon, 4 May 2026 14:57:15 +0200	[thread overview]
Message-ID: <9ece279f-2f57-466a-9af1-9fc8670c8ef9@oss.qualcomm.com> (raw)
In-Reply-To: <20260427170505.1494703-2-umang.chheda@oss.qualcomm.com>

On 4/27/26 7:05 PM, Umang Chheda wrote:
> The monaco-ac EVK is a new board variant which shares the majority of
> its hardware description with the existing monaco-evk board.
> 
> In preparation for adding this variant, extract the common hardware
> nodes from monaco-evk.dts into a new shared monaco-evk-common.dtsi
> include file, and update monaco-evk.dts to include it and keep only
> board-specific overrides.
> 
> No functional change intended.
> 
> Signed-off-by: Umang Chheda <umang.chheda@oss.qualcomm.com>
> ---

The patch is a bit difficult to view as-is, but the gist of it is that
the resulting monaco-evk.dts is:

// SPDX-License-Identifier: BSD-3-Clause
/*
 * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
 */

/dts-v1/;

#include "monaco-evk-common.dtsi"

/ {
	model = "Qualcomm Technologies, Inc. Monaco EVK";
	compatible = "qcom,monaco-evk", "qcom,qcs8300";

	/* This comes from a PMIC handled within the SAIL domain */
	vreg_s2s: vreg-s2s {
		compatible = "regulator-fixed";
		regulator-name = "vreg_s2s";

		regulator-min-microvolt = <1800000>;
		regulator-max-microvolt = <1800000>;
	};
};

&sdhc_1 {
	vmmc-supply = <&vreg_l8a>;
	vqmmc-supply = <&vreg_s2s>;

	no-sd;
	no-sdio;
	non-removable;

	status = "okay";
};


which begs the question - is the eMMC only there on the non-AC SKU?

Konrad

  reply	other threads:[~2026-05-04 12:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 17:05 [PATCH v4 0/4] arm64: dts: qcom: Introduce support for monaco-ac-evk Umang Chheda
2026-04-27 17:05 ` [PATCH v4 1/4] arm64: dts: qcom: monaco-evk: Extract common EVK hardware into shared dtsi Umang Chheda
2026-05-04 12:57   ` Konrad Dybcio [this message]
2026-05-04 18:28     ` Umang Chheda
2026-05-04 20:19     ` Krzysztof Kozlowski
2026-05-05 13:53       ` Umang Chheda
2026-05-04 18:44   ` Dmitry Baryshkov
2026-05-04 19:26     ` Umang Chheda
2026-05-04 23:28       ` Dmitry Baryshkov
2026-05-05 13:47         ` Umang Chheda
2026-04-27 17:05 ` [PATCH v4 2/4] dt-bindings: arm: qcom: Add monaco-ac-evk support Umang Chheda
2026-04-27 17:05 ` [PATCH v4 3/4] arm64: dts: qcom: monaco: Add monaco-ac EVK board Umang Chheda
2026-05-04 12:53   ` Konrad Dybcio
2026-05-04 19:16     ` Umang Chheda
2026-04-27 17:05 ` [PATCH v4 4/4] arm64: dts: qcom: monaco-ac-evk: Add IFP mezzanine 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=9ece279f-2f57-466a-9af1-9fc8670c8ef9@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=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