From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 919C1C4338F for ; Wed, 28 Jul 2021 14:51:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6C3AA60F91 for ; Wed, 28 Jul 2021 14:51:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236805AbhG1Ov5 (ORCPT ); Wed, 28 Jul 2021 10:51:57 -0400 Received: from foss.arm.com ([217.140.110.172]:58114 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235345AbhG1Ov4 (ORCPT ); Wed, 28 Jul 2021 10:51:56 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 9E8131042; Wed, 28 Jul 2021 07:51:54 -0700 (PDT) Received: from bogus (unknown [10.57.37.191]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 8235B3F70D; Wed, 28 Jul 2021 07:51:50 -0700 (PDT) Date: Wed, 28 Jul 2021 15:50:33 +0100 From: Sudeep Holla To: Cristian Marussi Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, virtualization@lists.linux-foundation.org, virtio-dev@lists.oasis-open.org, james.quinlan@broadcom.com, Jonathan.Cameron@Huawei.com, f.fainelli@gmail.com, etienne.carriere@linaro.org, vincent.guittot@linaro.org, souvik.chakravarty@arm.com, igor.skalkin@opensynergy.com, peter.hilber@opensynergy.com, alex.bennee@linaro.org, jean-philippe@linaro.org, mikhail.golubev@opensynergy.com, anton.yakovlev@opensynergy.com, Vasyl.Vavrychuk@opensynergy.com, Sudeep Holla , Andriy.Tryshnivskyy@opensynergy.com Subject: Re: [PATCH v6 11/17] firmware: arm_scmi: Make SCMI transports configurable Message-ID: <20210728145033.wpobgpxane2t2brc@bogus> References: <20210712141833.6628-1-cristian.marussi@arm.com> <20210712141833.6628-12-cristian.marussi@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210712141833.6628-12-cristian.marussi@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 12, 2021 at 03:18:27PM +0100, Cristian Marussi wrote: > Add configuration options to be able to select which SCMI transports have > to be compiled into the SCMI stack. > > Mailbox and SMC are by default enabled if their related dependencies are > satisfied. > > While doing that move all SCMI related config options in their own > dedicated submenu. > > Signed-off-by: Cristian Marussi > --- > Used a BUILD_BUG_ON() to avoid the scenario where SCMI is configured > without any transport. Coul dnot do in any other way in Kconfig due to > circular dependencies. > > This will be neeed later on to add new Virtio based transport and > optionally exclude other transports. > --- > drivers/firmware/Kconfig | 34 +-------------- > drivers/firmware/arm_scmi/Kconfig | 70 ++++++++++++++++++++++++++++++ > drivers/firmware/arm_scmi/Makefile | 4 +- > drivers/firmware/arm_scmi/common.h | 4 +- > drivers/firmware/arm_scmi/driver.c | 6 ++- > 5 files changed, 80 insertions(+), 38 deletions(-) > create mode 100644 drivers/firmware/arm_scmi/Kconfig > > diff --git a/drivers/firmware/Kconfig b/drivers/firmware/Kconfig > index 1db738d5b301..8d41f73f5395 100644 > --- a/drivers/firmware/Kconfig > +++ b/drivers/firmware/Kconfig > @@ -6,39 +6,7 @@ > > menu "Firmware Drivers" > > -config ARM_SCMI_PROTOCOL > - tristate "ARM System Control and Management Interface (SCMI) Message Protocol" > - depends on ARM || ARM64 || COMPILE_TEST > - depends on MAILBOX || HAVE_ARM_SMCCC_DISCOVERY > - help > - ARM System Control and Management Interface (SCMI) protocol is a > - set of operating system-independent software interfaces that are > - used in system management. SCMI is extensible and currently provides > - interfaces for: Discovery and self-description of the interfaces > - it supports, Power domain management which is the ability to place > - a given device or domain into the various power-saving states that > - it supports, Performance management which is the ability to control > - the performance of a domain that is composed of compute engines > - such as application processors and other accelerators, Clock > - management which is the ability to set and inquire rates on platform > - managed clocks and Sensor management which is the ability to read > - sensor data, and be notified of sensor value. > - > - This protocol library provides interface for all the client drivers > - making use of the features offered by the SCMI. > - > -config ARM_SCMI_POWER_DOMAIN > - tristate "SCMI power domain driver" > - depends on ARM_SCMI_PROTOCOL || (COMPILE_TEST && OF) > - default y > - select PM_GENERIC_DOMAINS if PM > - help > - This enables support for the SCMI power domains which can be > - enabled or disabled via the SCP firmware > - > - This driver can also be built as a module. If so, the module > - will be called scmi_pm_domain. Note this may needed early in boot > - before rootfs may be available. > +source "drivers/firmware/arm_scmi/Kconfig" > > config ARM_SCPI_PROTOCOL > tristate "ARM System Control and Power Interface (SCPI) Message Protocol" > diff --git a/drivers/firmware/arm_scmi/Kconfig b/drivers/firmware/arm_scmi/Kconfig > new file mode 100644 > index 000000000000..479fc8a3533e > --- /dev/null > +++ b/drivers/firmware/arm_scmi/Kconfig > @@ -0,0 +1,70 @@ > +# SPDX-License-Identifier: GPL-2.0-only > +menu "ARM System Control and Management Interface Protocol" > + > +config ARM_SCMI_PROTOCOL > + tristate "ARM System Control and Management Interface (SCMI) Message Protocol" > + depends on ARM || ARM64 || COMPILE_TEST > + help > + ARM System Control and Management Interface (SCMI) protocol is a > + set of operating system-independent software interfaces that are > + used in system management. SCMI is extensible and currently provides > + interfaces for: Discovery and self-description of the interfaces > + it supports, Power domain management which is the ability to place > + a given device or domain into the various power-saving states that > + it supports, Performance management which is the ability to control > + the performance of a domain that is composed of compute engines > + such as application processors and other accelerators, Clock > + management which is the ability to set and inquire rates on platform > + managed clocks and Sensor management which is the ability to read > + sensor data, and be notified of sensor value. > + > + This protocol library provides interface for all the client drivers > + making use of the features offered by the SCMI. > + May be you can add if condition here to remove the depends on ARM_SCMI_PROTOCOL if ARM_SCMI_PROTOCOL > +config ARM_SCMI_HAVE_TRANSPORT > + bool > + help > + This declares whether at least one SCMI transport has been configured. > + Used to trigger a build bug when trying to build SCMI without any > + configured transport. > + > +config ARM_SCMI_TRANSPORT_MAILBOX > + bool "SCMI transport based on Mailbox" > + depends on ARM_SCMI_PROTOCOL && MAILBOX And drop ARM_SCMI_PROTOCOL above > + select ARM_SCMI_HAVE_TRANSPORT > + default y Do we need a user visible choice if it is always default on ? > + help > + Enable mailbox based transport for SCMI. > + > + If you want the ARM SCMI PROTOCOL stack to include support for a > + transport based on mailboxes, answer Y. > + A matching DT entry will also be needed to indicate the effective > + presence of this kind of transport. > + I would drop the above comment on matching DT. > +config ARM_SCMI_TRANSPORT_SMC > + bool "SCMI transport based on SMC" > + depends on ARM_SCMI_PROTOCOL && HAVE_ARM_SMCCC_DISCOVERY Ditto > + select ARM_SCMI_HAVE_TRANSPORT > + default y > + help > + Enable SMC based transport for SCMI. > + > + If you want the ARM SCMI PROTOCOL stack to include support for a > + transport based on SMC, answer Y. > + A matching DT entry will also be needed to indicate the effective > + presence of this kind of transport. > + endif #ARM_SCMI_PROTOCOL -- Regards, Sudeep