[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZsSsq_Do-KEyy7vU@bogus>
Date: Tue, 20 Aug 2024 15:48:11 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: 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,
quic_nkela@...cinc.com, dan.carpenter@...aro.org,
Sudeep Holla <sudeep.holla@....com>, 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 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
Powered by blists - more mailing lists