From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: smem: Update max processor count
Date: Wed, 1 Apr 2026 10:25:05 +0200 [thread overview]
Message-ID: <25a0cd52-ea99-47a8-9965-18a1e6e0687b@oss.qualcomm.com> (raw)
In-Reply-To: <dopgyc65xh2ei3oebltbzrog2jkpwzoz2fu4b4vmpsolmaziva@qtfbuipbeneo>
On 3/31/26 7:57 PM, Dmitry Baryshkov wrote:
> On Tue, Mar 31, 2026 at 09:54:39PM +0530, Mukesh Ojha wrote:
>> Update max processor count to reflect the number of co-processors on
>> upcoming SoC.
>>
>> Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
>> ---
>> drivers/soc/qcom/smem.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/soc/qcom/smem.c b/drivers/soc/qcom/smem.c
>> index d5c94b47f431..8daa25d16fdc 100644
>> --- a/drivers/soc/qcom/smem.c
>> +++ b/drivers/soc/qcom/smem.c
>> @@ -86,7 +86,7 @@
>> #define SMEM_GLOBAL_HOST 0xfffe
>>
>> /* Max number of processors/hosts in a system */
>> -#define SMEM_HOST_COUNT 25
>> +#define SMEM_HOST_COUNT 30
>
> Would it be possible to get rid of this constant at all?
I've seen a patch in pre-review to do just that. I'll poke the author.
Konrad
next prev parent reply other threads:[~2026-04-01 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 16:24 Mukesh Ojha
2026-03-31 17:57 ` Dmitry Baryshkov
2026-04-01 8:25 ` Konrad Dybcio [this message]
2026-04-01 10:28 ` Mukesh Ojha
-- strict thread matches above, loose matches on Subject: below --
2025-04-24 23:45 Unnathi Chalicheemala
2025-04-25 8:13 ` Konrad Dybcio
2025-05-09 22:13 ` 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=25a0cd52-ea99-47a8-9965-18a1e6e0687b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.ojha@oss.qualcomm.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®