Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Aelin Reidel <aelin@mainlining.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, linux@mainlining.org,
	 phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	 Aelin Reidel <aelin@mainlining.org>
Subject: [PATCH v2 0/2] Add SM7450 and SM7450P to socinfo
Date: Mon, 02 Mar 2026 14:10:13 +0100	[thread overview]
Message-ID: <20260302-fillmore-socids-v2-0-e6c5ad167ec4@mainlining.org> (raw)

Add the SoC IDs of SM7450 and SM7450P, two SoCs in the fillmore family,
to socinfo.

Signed-off-by: Aelin Reidel <aelin@mainlining.org>
---
Changes in v2:
- Fix sorting in soc_id list (Krzysztof)
- Link to v1: https://lore.kernel.org/r/20260301-fillmore-socids-v1-0-5a033cd8d0e3@mainlining.org

---
Aelin Reidel (2):
      dt-bindings: arm: qcom,ids: Add SoC IDs for SM7450 and SM7450P
      soc: qcom: socinfo: Add SoC IDs for SM7450 and SM7450P

 drivers/soc/qcom/socinfo.c         | 2 ++
 include/dt-bindings/arm/qcom,ids.h | 2 ++
 2 files changed, 4 insertions(+)
---
base-commit: 3fa5e5702a82d259897bd7e209469bc06368bf31
change-id: 20260301-fillmore-socids-a5cfb25ae225

Best regards,
-- 
Aelin Reidel <aelin@mainlining.org>


             reply	other threads:[~2026-03-02 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 13:10 Aelin Reidel [this message]
2026-03-02 13:10 ` [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC IDs for SM7450 and SM7450P Aelin Reidel
2026-03-03  6:41   ` Krzysztof Kozlowski
2026-03-02 13:10 ` [PATCH v2 2/2] soc: qcom: socinfo: " Aelin Reidel
2026-03-03  6:41   ` Krzysztof Kozlowski
2026-03-16  2:02 ` [PATCH v2 0/2] Add SM7450 and SM7450P to socinfo 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=20260302-fillmore-socids-v2-0-e6c5ad167ec4@mainlining.org \
    --to=aelin@mainlining.org \
    --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=linux@mainlining.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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