public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sumit Garg <sumit.garg@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-kernel@vger.kernel.org, bsatish@qti.qualcomm.com,
	akhiverm@qti.qualcomm.com, nicolas.dechesne@oss.qualcomm.com,
	Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: qrb2210-arduino-imola: Drop modem support
Date: Mon, 27 Apr 2026 13:43:08 +0200	[thread overview]
Message-ID: <c037803d-d33f-47a6-8db2-736c7b49092b@oss.qualcomm.com> (raw)
In-Reply-To: <20260427112833.1160332-2-sumit.garg@kernel.org>

On 4/27/26 1:28 PM, Sumit Garg wrote:
> From: Sumit Garg <sumit.garg@oss.qualcomm.com>
> 
> QRB2210 has modem fused out as it's only available on the mobile variant
> which is QCM2290. So let's disable modem support from Arduino Imola/UNO-Q.
> 
> Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
> ---

On previous APQ-y SoCs, the remoteproc was still physically present and
served various functions (among others, GPS, IIRC). Is that not the case?

Konrad


  reply	other threads:[~2026-04-27 11:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 11:28 [PATCH 1/2] arm64: dts: qcom: qrb2210-rb1: Drop modem support Sumit Garg
2026-04-27 11:28 ` [PATCH 2/2] arm64: dts: qcom: qrb2210-arduino-imola: " Sumit Garg
2026-04-27 11:43   ` Konrad Dybcio [this message]
2026-04-27 11:54     ` Sumit Garg
2026-04-27 12:46       ` Konrad Dybcio
2026-04-27 15:40 ` [PATCH 1/2] arm64: dts: qcom: qrb2210-rb1: " Dmitry Baryshkov
2026-05-01  5:37   ` Sumit Garg

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=c037803d-d33f-47a6-8db2-736c7b49092b@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=akhiverm@qti.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bsatish@qti.qualcomm.com \
    --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=nicolas.dechesne@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=sumit.garg@kernel.org \
    --cc=sumit.garg@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