Devicetree
 help / color / mirror / Atom feed
From: David Heidelberg via B4 Relay <devnull+david.ixit.cz@kernel.org>
To: 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, David Heidelberg <david@ixit.cz>
Subject: [PATCH v2 0/2] Recognize Snapdragon SDM850
Date: Sat, 27 Jun 2026 19:50:14 +0200	[thread overview]
Message-ID: <20260627-sda850-v2-0-44bf46ade42e@ixit.cz> (raw)

Useful for sdm850 devices in tree and also will be used by Comma AI comma three

Signed-off-by: David Heidelberg <david@ixit.cz>
---
Changes in v2:
- It's not SDA850, but classic SDM850. (Konrad)
- Add consumer of the define (socinfo). (Krzysztof)
- Link to v1: https://lore.kernel.org/r/20260623-sda850-v1-1-ddd8e62c85d8@ixit.cz

---
David Heidelberg (2):
      dt-bindings: arm: qcom,ids: Add SoC ID for Snapdragon SDM 850
      soc: qcom: socinfo: Add SoC ID for SDM850

 drivers/soc/qcom/socinfo.c         | 1 +
 include/dt-bindings/arm/qcom,ids.h | 1 +
 2 files changed, 2 insertions(+)
---
base-commit: 948efecf22e49aa4bf55bb73ec79a0ddcfd38571
change-id: 20260623-sda850-6b5c1e44662c

Best regards,
-- 
David Heidelberg <david@ixit.cz>



             reply	other threads:[~2026-06-27 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27 17:50 David Heidelberg via B4 Relay [this message]
2026-06-27 17:50 ` [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for Snapdragon SDM 850 David Heidelberg via B4 Relay
2026-06-29  7:00   ` Krzysztof Kozlowski
2026-06-29  8:19   ` Konrad Dybcio
2026-06-27 17:50 ` [PATCH v2 2/2] soc: qcom: socinfo: Add SoC ID for SDM850 David Heidelberg via B4 Relay
2026-06-29  7:00   ` Krzysztof Kozlowski

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=20260627-sda850-v2-0-44bf46ade42e@ixit.cz \
    --to=devnull+david.ixit.cz@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=david@ixit.cz \
    --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=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