From: Robert Marko <robimarko@gmail.com>
To: Naman Jain <quic_namajain@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_pkondeti@quicinc.com, quic_kaushalk@quicinc.com
Subject: Re: [PATCH 1/2] soc: qcom: socinfo: Add support for new fields in revision 18
Date: Tue, 6 Jun 2023 12:33:15 +0200 [thread overview]
Message-ID: <955b8b78-eb50-7ee2-f5f7-6b66a2daa963@gmail.com> (raw)
In-Reply-To: <20230602032600.14790-1-quic_namajain@quicinc.com>
On 02. 06. 2023. 05:25, Naman Jain wrote:
> Add support for below fields coming in socinfo structure under v18:
> * num_kvps: number of key value pairs (KVP)
> * kvps_offset: the offset of the KVP table from the base address of
> socinfo structure in SMEM
> KVP table has boolean values for certain feature flags, used to determine
> hardware configuration.
>
> Signed-off-by: Naman Jain <quic_namajain@quicinc.com>
Hi,
The socinfo struct itself was moved into a separate header[1] so it can
be reused,
so this patch series needs to be rebased on top of linux-next.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/include/linux/soc/qcom/socinfo.h?h=next-20230606&id=ec001bb71e4476f7f5be9db693d5f43e65b9d8cb
Regards,
Robert
> ---
> drivers/soc/qcom/socinfo.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/soc/qcom/socinfo.c b/drivers/soc/qcom/socinfo.c
> index c2e4a57dd666..a76006ea8a37 100644
> --- a/drivers/soc/qcom/socinfo.c
> +++ b/drivers/soc/qcom/socinfo.c
> @@ -181,6 +181,9 @@ struct socinfo {
> __le32 nnum_partname_mapping;
> /* Version 17 */
> __le32 oem_variant;
> + /* Version 18 */
> + __le32 num_kvps;
> + __le32 kvps_offset;
> };
>
> #ifdef CONFIG_DEBUG_FS
> @@ -620,6 +623,7 @@ static void socinfo_debugfs_init(struct qcom_socinfo *qcom_socinfo,
> &qcom_socinfo->info.fmt);
>
> switch (qcom_socinfo->info.fmt) {
> + case SOCINFO_VERSION(0, 18):
> case SOCINFO_VERSION(0, 17):
> qcom_socinfo->info.oem_variant = __le32_to_cpu(info->oem_variant);
> debugfs_create_u32("oem_variant", 0444, qcom_socinfo->dbg_root,
>
next prev parent reply other threads:[~2023-06-06 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 3:25 Naman Jain
2023-06-02 3:26 ` [PATCH 2/2] soc: qcom: socinfo: Add support for new fields in revision 19 Naman Jain
2023-06-06 10:33 ` Robert Marko [this message]
2023-06-06 10:41 ` [PATCH 1/2] soc: qcom: socinfo: Add support for new fields in revision 18 Naman Jain
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=955b8b78-eb50-7ee2-f5f7-6b66a2daa963@gmail.com \
--to=robimarko@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kaushalk@quicinc.com \
--cc=quic_namajain@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
/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®