From mboxrd@z Thu Jan 1 00:00:00 1970 From: Niklas Cassel Subject: Re: [PATCH] soc: qcom: qmi: add a prompt to QCOM_QMI_HELPERS Date: Fri, 28 Sep 2018 16:00:25 +0200 Message-ID: <20180928140025.GB5610@centauri.lan> References: <20180427140358.30839-1-elder@linaro.org> <20180928122616.GA5249@centauri.lan> <4025f206-631a-55e9-9b7a-89dcf3370284@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4025f206-631a-55e9-9b7a-89dcf3370284@linaro.org> Sender: linux-kernel-owner@vger.kernel.org To: Alex Elder , bjorn.andersson@linaro.org, srinivas.kandagatla@linaro.org Cc: andy.gross@linaro.org, david.brown@linaro.org, linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org On Fri, Sep 28, 2018 at 08:23:03AM -0500, Alex Elder wrote: > On 09/28/2018 07:26 AM, Niklas Cassel wrote: > > On Fri, Sep 28, 2018 at 06:41:11AM -0500, Alex Elder wrote: > >> Was there something wrong with this patch? I sent it a long time > >> ago but it still applies cleanly. I can re-send if you like. > > > > Hello Alex, > > > > This patch does not apply on top of > > https://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git/log/?h=for-next > > Sorry, I sent this before I tracked down where Andy's for-next > tree was. It applied OK to linus/master. > > > When you don't specify a string for a Kconfig, then you won't be able to > > select it via menuconfig, only through other Kconfigs, e.g.: > > $ git grep QCOM_QMI_HELPERS > > drivers/remoteproc/Kconfig: select QCOM_QMI_HELPERS > > > > What Kconfig is it that needs QCOM_QMI_HELPERS? > > IPA, which is not yet merged. > > The entry in "drivers/soc/qcom/Kconfig" for this option includes > help text, so I presume it was an oversight not to include a > string (prompt). It is the only non-trivial entry in that file > that does not include one. Why should this entry not be listed > in menus? I see. Indeed it is a bit confusing that it has a help text. > > > Why do you need to make is selectable via menuconfig? > > Isn't it sufficient to add a "select QCOM_QMI_HELPERS" to that Kconfig? > > I have CONFIG_IPA dependent on CONFIG_QCOM_QMI_HELPERS. I could > change that to select it instead but I still think this entry > should be changed. > > I'll mention that SLIM_QCOM_NGD_CTRL in drivers/slimbus/Kconfig > also depends on--rather than selects--QCOM_QMI_HELPERS. I would have expected SLIM_QCOM_NGD_CTRL to select rather than depend. But then it is also weird that QCOM_QMI_HELPERS has a help text. I guess Bjorn should answer how this Kconfig was intended to be used, because right now it is kind of ambiguous. Kind regards, Niklas > > -Alex > > > > > Kind regards, > > Niklas > > > >> > >> -Alex > >> > >> On 04/27/2018 09:03 AM, Alex Elder wrote: > >>> Add a prompt to the "tristate" attribute in the Kconfig file in > >>> which QCOM_QMI_HELPERS is defined; I find it doesn't get selected > >>> without it. > >>> > >>> Signed-off-by: Alex Elder > >>> --- > >>> drivers/soc/qcom/Kconfig | 2 +- > >>> 1 file changed, 1 insertion(+), 1 deletion(-) > >>> > >>> diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig > >>> index 5c4535b545cc..81a501765cd9 100644 > >>> --- a/drivers/soc/qcom/Kconfig > >>> +++ b/drivers/soc/qcom/Kconfig > >>> @@ -36,7 +36,7 @@ config QCOM_PM > >>> low power modes. > >>> > >>> config QCOM_QMI_HELPERS > >>> - tristate > >>> + tristate "Qualcomm QMI Helpers" > >>> depends on ARCH_QCOM && NET > >>> help > >>> Helper library for handling QMI encoded messages. QMI encoded > >>> > >> >