public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: add Dragonboard 820c using APQ8096SG SoC
Date: Wed, 12 Nov 2025 11:45:45 +0100	[thread overview]
Message-ID: <103ff788-54cf-4c26-9465-165f03ecae04@oss.qualcomm.com> (raw)
In-Reply-To: <20251111-db820c-pro-v1-1-6eece16c5c23@oss.qualcomm.com>

On 11/11/25 5:02 PM, Dmitry Baryshkov wrote:
> There exists a variant of the DB820c board, using the APQ8096SG
> (MSM8996 Pro) SoC. Describe it in the bindings.

Apparently it's an IoT SKU:

https://www.qualcomm.com/processors/application-processors/products/apq8096sg

Konrad

  reply	other threads:[~2025-11-12 10:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-11 16:02 [PATCH 0/2] arm64: dts: qcom: add AP8096SG variant of DB820c Dmitry Baryshkov
2025-11-11 16:02 ` [PATCH 1/2] dt-bindings: arm: qcom: add Dragonboard 820c using APQ8096SG SoC Dmitry Baryshkov
2025-11-12 10:45   ` Konrad Dybcio [this message]
2025-11-17 17:49   ` Rob Herring (Arm)
2025-11-11 16:02 ` [PATCH 2/2] arm64: dts: qcom: add apq8096sg-db820c, AP8096SG variant of DB820c Dmitry Baryshkov
2025-11-12  9:44   ` Konrad Dybcio
2025-11-13 20:32     ` Dmitry Baryshkov
2025-11-14 21:31       ` Konrad Dybcio
2025-11-15  0:09         ` Dmitry Baryshkov
2025-11-17 11:54           ` Konrad Dybcio
2026-01-14  0:12             ` Dmitry Baryshkov
2026-01-14  9:28               ` Konrad Dybcio
2025-11-12 13:56 ` [PATCH 0/2] arm64: dts: qcom: add " Rob Herring (Arm)
2025-11-12 14:26   ` Rob Herring (Arm)
2026-02-27  3:46 ` Bjorn Andersson

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=103ff788-54cf-4c26-9465-165f03ecae04@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=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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