From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: smem: support Glymur DRAM info
Date: Mon, 24 Aug 2026 16:38:56 +0200 [thread overview]
Message-ID: <64c426be-bed9-4ed5-ad46-2b9c45d0826b@oss.qualcomm.com> (raw)
In-Reply-To: <zwpgeeapcjwtad7xyerz3bdegrtbuu2ajdqt5yjpcvxgopq3kq@cg2uvzmdtwyh>
On 8/20/26 9:31 PM, Abel Vesa wrote:
> On 26-08-20 18:30:08, Konrad Dybcio wrote:
>> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>>
>> Glymur firmware provides a version 7 DDR-info SMEM entry whose 872-byte
>> layout is different from the one the driver supports today.
>>
>> The data contains 16 channel descriptors, 14 DDR frequency slots, four
>> 4 DDR region slots, a 10-entry SHUB frequency plan, and v6 misc information.
>> It accounts for 616 bytes; the captured SMEM entry has a further 256
>> zero bytes.
[...]
>> @@ -39,6 +49,7 @@ enum ddr_info_version {
>> INFO_V6, /* INFO_V6 seems to only have shipped with 6 DDR regions, unlike V7 */
>> INFO_V7,
>> INFO_V7_WITH_6_REGIONS,
>> + INFO_V7_GLYMUR,
>
> Just curious, isn't there like a minor version number that could be
> used instead of the GLYMUR suffix here?
There are no minor versions, it's really more of a "version 7 baseline
with X regions, with Y shub frequencies, max of Z channels and somehow
lots of extra zero padding at the end".
This is unfortunately a huge mess..
Konrad
next prev parent reply other threads:[~2026-08-24 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 16:30 Konrad Dybcio
2026-08-20 19:31 ` Abel Vesa
2026-08-24 14:38 ` Konrad Dybcio [this message]
2026-08-25 10:24 ` Gopikrishna Garmidi
2026-08-26 13:11 ` Konrad Dybcio
2026-08-31 17:53 ` 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=64c426be-bed9-4ed5-ad46-2b9c45d0826b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®