From: Kathiravan T <quic_kathirav@quicinc.com>
To: Robert Marko <robimarko@gmail.com>, <agross@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>,
<ilia.lin@kernel.org>, <rafael@kernel.org>,
<viresh.kumar@linaro.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-pm@vger.kernel.org>
Cc: <ansuelsmth@gmail.com>
Subject: Re: [PATCH v3 3/5] soc: qcom: smem: introduce qcom_smem_get_msm_id()
Date: Thu, 25 May 2023 18:28:59 +0530 [thread overview]
Message-ID: <c4a50acd-2c0a-7c18-95d8-e9145fa1ff24@quicinc.com> (raw)
In-Reply-To: <20230525120956.3095317-3-robimarko@gmail.com>
On 5/25/2023 5:39 PM, Robert Marko wrote:
> Introduce a helper to return the SoC SMEM ID, which is used to identify the
> exact SoC model as there may be differences in the same SoC family.
>
> Currently, cpufreq-nvmem does this completely in the driver and there has
> been more interest expresed for other drivers to use this information so
> lets expose a common helper to prevent redoing it in individual drivers
> since this field is present on every SMEM table version.
>
> Signed-off-by: Robert Marko <robimarko@gmail.com>
> ---
> Changes in v3:
> * Change export to EXPORT_SYMBOL_GPL
> * Use an argument for returning SoC ID
> * Update kerneldoc
> ---
> drivers/soc/qcom/smem.c | 24 ++++++++++++++++++++++++
> include/linux/soc/qcom/smem.h | 2 ++
> 2 files changed, 26 insertions(+)
>
> diff --git a/drivers/soc/qcom/smem.c b/drivers/soc/qcom/smem.c
> index bc98520c4969..185ed0da11a1 100644
> --- a/drivers/soc/qcom/smem.c
> +++ b/drivers/soc/qcom/smem.c
> @@ -14,6 +14,7 @@
> #include <linux/sizes.h>
> #include <linux/slab.h>
> #include <linux/soc/qcom/smem.h>
> +#include <linux/soc/qcom/socinfo.h>
>
> /*
> * The Qualcomm shared memory system is a allocate only heap structure that
> @@ -772,6 +773,29 @@ phys_addr_t qcom_smem_virt_to_phys(void *p)
> }
> EXPORT_SYMBOL_GPL(qcom_smem_virt_to_phys);
>
> +/**
> + * qcom_smem_get_msm_id() - return the SoC ID
> + * @id: On success, we return the SoC ID here.
> + *
> + * Look up SoC ID from HW/SW build ID and return it.
> + *
> + * Return: 0 on success, negative errno on failure.
> + */
> +int qcom_smem_get_msm_id(u32 *id)
I think, MSM is not the only platform which will leverage this API.
qcom_smem_get_soc_id() / qcom_smem_get_cpu_id() would make more sense
than qcom_smem_get_msm_id() ?
> +{
> + size_t len;
> + struct socinfo *info;
> +
> + info = qcom_smem_get(QCOM_SMEM_HOST_ANY, SMEM_HW_SW_BUILD_ID, &len);
len is unused after this, can we just pass NULL? Did a quick check on
the code, if we pass the address, size of the item will be updated, else no.
> + if (IS_ERR(info))
> + return PTR_ERR(info);
> +
> + *id = info->id;
> +
> + return 0;
> +}
> +EXPORT_SYMBOL_GPL(qcom_smem_get_msm_id);
> +
> static int qcom_smem_get_sbl_version(struct qcom_smem *smem)
> {
> struct smem_header *header;
> diff --git a/include/linux/soc/qcom/smem.h b/include/linux/soc/qcom/smem.h
> index 86e1b358688a..cb204ad6373c 100644
> --- a/include/linux/soc/qcom/smem.h
> +++ b/include/linux/soc/qcom/smem.h
> @@ -11,4 +11,6 @@ int qcom_smem_get_free_space(unsigned host);
>
> phys_addr_t qcom_smem_virt_to_phys(void *p);
>
> +int qcom_smem_get_msm_id(u32 *id);
> +
> #endif
next prev parent reply other threads:[~2023-05-25 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 12:09 [PATCH v3 1/5] soc: qcom: socinfo: move SMEM item struct and defines to a header Robert Marko
2023-05-25 12:09 ` [PATCH v3 2/5] soc: qcom: smem: Switch to EXPORT_SYMBOL_GPL() Robert Marko
2023-05-25 12:12 ` Konrad Dybcio
2023-05-25 20:21 ` Trilok Soni
2023-05-25 21:06 ` Trilok Soni
2023-05-25 12:09 ` [PATCH v3 3/5] soc: qcom: smem: introduce qcom_smem_get_msm_id() Robert Marko
2023-05-25 12:58 ` Kathiravan T [this message]
2023-05-25 15:03 ` Robert Marko
2023-05-25 21:21 ` Konrad Dybcio
2023-05-25 21:36 ` Konrad Dybcio
2023-05-25 12:09 ` [PATCH v3 4/5] cpufreq: qcom-nvmem: use SoC ID-s from bindings Robert Marko
2023-05-25 12:09 ` [PATCH v3 5/5] cpufreq: qcom-nvmem: use helper to get SMEM SoC ID Robert Marko
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=c4a50acd-2c0a-7c18-95d8-e9145fa1ff24@quicinc.com \
--to=quic_kathirav@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=ilia.lin@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robimarko@gmail.com \
--cc=viresh.kumar@linaro.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®