linux-kernel - Re: [RFC 4/7] soc: qcom: Utilize qcom scmi vendor protocol for bus dvfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZeCUYVnZ8ZTRBobV@bogus>
Date: Thu, 29 Feb 2024 14:27:45 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Sibi Sankar <quic_sibis@...cinc.com>
Cc: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
	Sudeep Holla <sudeep.holla@....com>, <cristian.marussi@....com>,
	<andersson@...nel.org>, <konrad.dybcio@...aro.org>,
	<jassisinghbrar@...il.com>, <robh+dt@...nel.org>,
	<krzysztof.kozlowski+dt@...aro.org>, <linux-kernel@...r.kernel.org>,
	<linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<quic_rgottimu@...cinc.com>, <quic_kshivnan@...cinc.com>,
	<conor+dt@...nel.org>, Amir Vajid <avajid@...cinc.com>
Subject: Re: [RFC 4/7] soc: qcom: Utilize qcom scmi vendor protocol for bus
 dvfs

On Mon, Feb 12, 2024 at 03:54:27PM +0530, Sibi Sankar wrote:
> 
> 
> On 1/18/24 02:11, Dmitry Baryshkov wrote:
> > On Wed, 17 Jan 2024 at 19:36, Sibi Sankar <quic_sibis@...cinc.com> wrote:
> > > 
> > > From: Shivnandan Kumar <quic_kshivnan@...cinc.com>
> > > 
> > > This patch introduces a client driver that interacts with the SCMI QCOM
> > 
> > git grep This.patch Documentation/process/
> > 
> > > vendor protocol and passes on the required tuneables to start various
> > > features running on the SCMI controller.
> > 
> > Is there any word about the 'memlat'? No. Unless one  reads into the
> > patch, one can not come up with the idea of what is being introduced.
> 
> ack, will fix it in the re-spin.
> 
> > 
> > > 
> > > Signed-off-by: Shivnandan Kumar <quic_kshivnan@...cinc.com>
> > > Co-developed-by: Ramakrishna Gottimukkula <quic_rgottimu@...cinc.com>
> > > Signed-off-by: Ramakrishna Gottimukkula <quic_rgottimu@...cinc.com>
> > > Co-developed-by: Amir Vajid <avajid@...cinc.com>
> > > Signed-off-by: Amir Vajid <avajid@...cinc.com>
> > > Co-developed-by: Sibi Sankar <quic_sibis@...cinc.com>
> > > Signed-off-by: Sibi Sankar <quic_sibis@...cinc.com>
> > > ---
> > >   drivers/soc/qcom/Kconfig            |  10 +
> > >   drivers/soc/qcom/Makefile           |   1 +
> > >   drivers/soc/qcom/qcom_scmi_client.c | 486 ++++++++++++++++++++++++++++
> > 
> > Should it go to drivers/firmware/arm_scmi instead? Or maybe to drivers/devfreq?
> 
> I don't think it should go into arm_scmi unless Sudeep wants it there.

I won't comment or worry about those silly details yet. I would like to
understand the design better first and all these can be sorted when we
get closer to getting this merged.

-- 
Regards,
Sudeep