[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <34d1783c-8b0d-4337-8169-1c41cd02a6e3@quicinc.com>
Date: Thu, 12 Sep 2024 12:22:48 -0700
From: Nikunj Kela <quic_nkela@...cinc.com>
To: Sudeep Holla <sudeep.holla@....com>,
Cristian Marussi
<cristian.marussi@....com>
CC: <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<arm-scmi@...r.kernel.org>, <devicetree@...r.kernel.org>,
<james.quinlan@...adcom.com>, <f.fainelli@...il.com>,
<vincent.guittot@...aro.org>, <etienne.carriere@...com>,
<peng.fan@....nxp.com>, <michal.simek@....com>,
<quic_sibis@...cinc.com>, <dan.carpenter@...aro.org>,
<souvik.chakravarty@....com>, <robh@...nel.org>, <krzk+dt@...nel.org>
Subject: Re: [PATCH v1 5/6] firmware: arm_scmi: Use max_msg and max_msg_size
from devicetree
On 8/20/2024 7:48 AM, Sudeep Holla wrote:
> On Tue, Jul 30, 2024 at 03:47:06PM +0100, Cristian Marussi wrote:
>> Override max_msg and max_msg_size transport properties when corresponding
>> devicetree properties are available.
>>
> I am holding off on these changes to think how these max_msg and max_msg_size
> can be used without breaking any platforms allowing space for the header
> and the message itself which is around 28 bytes. The binding itself looks
> good. We may have to adjust the value passed to the core driver taking
> the above into consideration.
>
> --
> Regards,
> Sudeep
Hi Sudeep,
Qualcomm is interested in these parameters being configurable. Just
wanted to make sure you are aware.
Thanks,
-Nikunj
Powered by blists - more mailing lists