From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@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>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Cc: Abel Vesa <abel.vesa@oss.qualcomm.com>
Subject: Re: [PATCH 0/2] arm64: qcom: Add SoC ID for CQ7790S
Date: Mon, 19 Jan 2026 12:10:09 +0100 [thread overview]
Message-ID: <e0147302-66ce-419e-b421-fe850f8489e4@oss.qualcomm.com> (raw)
In-Reply-To: <f41a692f-c3a4-4948-8179-4628542f90f6@oss.qualcomm.com>
On 1/19/26 12:03 PM, Krzysztof Kozlowski wrote:
> On 19/01/2026 11:50, Konrad Dybcio wrote:
>> On 1/19/26 10:59 AM, Krzysztof Kozlowski wrote:
>>> Hi,
>>>
>>> This is early and first/initial posting for upstreaming Eliza SoC, e.g.
>>> CQ7790S IoT variant. AFAIK, there is also CQ7790M variant with different
>>> ID, but I do not have such hardware, thus only "S" goes here.
>>
>> If you're sure about this marketing name being assigned to a specific
>> SMEM ID, those *never* change after they're assigned, so it's fine if
>> you just add it to the list
>
> I don't know if I ever going to work on the M (modem) variant, so do you
> want to document it just for completeness?
If there's no internal reasons preventing you from it, sure
Konrad
next prev parent reply other threads:[~2026-01-19 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 9:59 [PATCH 0/2] arm64: qcom: Add SoC ID for CQ7790S Krzysztof Kozlowski
2026-01-19 9:59 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: " Krzysztof Kozlowski
2026-01-19 9:59 ` [PATCH 2/2] soc: qcom: socinfo: " Krzysztof Kozlowski
2026-01-19 10:50 ` [PATCH 0/2] arm64: qcom: " Konrad Dybcio
2026-01-19 11:03 ` Krzysztof Kozlowski
2026-01-19 11:10 ` Konrad Dybcio [this message]
2026-01-19 11:12 ` 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=e0147302-66ce-419e-b421-fe850f8489e4@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@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=krzysztof.kozlowski@oss.qualcomm.com \
--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