On Thu, May 07, 2026 at 03:28:21PM +0530, Sibi Sankar wrote: > > On 5/7/2026 2:40 PM, Dmitry Baryshkov wrote: > > On Thu, May 07, 2026 at 11:52:29AM +0530, Sibi Sankar wrote: > > > The QCOM SCMI vendor protocol provides a generic way of exposing a number > > > of > > > Qualcomm SoC specific features (like memory bus scaling) through a > > > mixture of > > > pre-determined algorithm strings and param_id pairs hosted on the SCMI > > > controller. On Qualcomm Glymur and Hamoa SoCs, the memlat governor and the > > > mechanism to control the various caches and ram is hosted on the CPU > > > Control > > > Processor (CPUCP) and the method to tweak and start the governor is > > > exposed > > > through the QCOM SCMI Generic Extension Protocol. > > > > Could you please clarify, does this apply to the common commercial > > Glymur and Hamoa laptops? > > Yes, they do apply to common commercial Glymur/Hamoa Laptops > as is. This is the same solution used on the windows side of things > as well. There can be certain cases like Johan has reported earlier > where certain oems are stuck with on older version of CPUCP > which requires a the memlat string to be sent out in lower case > we should be able to handle those as well with overriding those > by using driver data and specific compatibles.
Ack, thanks for the confirmation. -- With best wishes Dmitry
