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@xxxxxxxxxxx> wrote: > > > > > > From: Shivnandan Kumar <quic_kshivnan@xxxxxxxxxxx> > > > > > > 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@xxxxxxxxxxx> > > > Co-developed-by: Ramakrishna Gottimukkula <quic_rgottimu@xxxxxxxxxxx> > > > Signed-off-by: Ramakrishna Gottimukkula <quic_rgottimu@xxxxxxxxxxx> > > > Co-developed-by: Amir Vajid <avajid@xxxxxxxxxxx> > > > Signed-off-by: Amir Vajid <avajid@xxxxxxxxxxx> > > > Co-developed-by: Sibi Sankar <quic_sibis@xxxxxxxxxxx> > > > Signed-off-by: Sibi Sankar <quic_sibis@xxxxxxxxxxx> > > > --- > > > 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
