From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id ACE7F21FF2A for ; Mon, 19 Jan 2026 15:46:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768837571; cv=none; b=J9qbJc5aX7Icp9SCiWvy/B5IekngXl8tybXSZEiUpcgMmTNUEyLZjOBGURrLgkeDatdlDXkonqudGyAjPTNywpeKBtp4jzmGLAWQfAqno/4OLn+USxmE0yp9P2c9VwrFQC/WplNsUBE2cKklCLtkOz3FA9R9DJpu/lp8GBM28ok= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768837571; c=relaxed/simple; bh=HHiJmeX1MzIM4//+PCFgcmV4KVJ5+kw5PEneX0r4sKk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=qXgAaMsBaTEe/3RDw1Lirm0h1oAPzbt9nmqGudswMnc69WCCKC8KTTnEKtLc5IpThhdidCvvEB5mNFmf7Rh5cCGAeI5EMUhF67S8zyk9IIXkELVXuYEnSzHPD/JFdMolwMcp3cANzTDMFRqV1hTVl93Ub+xllne1aQe7wTPPnXY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com 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 8C6DDFEC; Mon, 19 Jan 2026 07:46:02 -0800 (PST) Received: from localhost (e132581.arm.com [10.1.196.87]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B89EF3F694; Mon, 19 Jan 2026 07:46:08 -0800 (PST) Date: Mon, 19 Jan 2026 15:46:06 +0000 From: Leo Yan To: James Clark Cc: Alexander Shishkin , linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org, linux-kernel@vger.kernel.org, Maxime Coquelin , Alexandre Torgue , Greg Kroah-Hartman Subject: Re: [PATCH] stm class: Fix Kconfig symbols Message-ID: <20260119154606.GE2732125@e132581.arm.com> References: <20251217-fix_stm_kconfig-v1-1-531fb3674549@arm.com> <8d48dd55-d78d-4cbf-88b0-5427a731ba7d@linaro.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8d48dd55-d78d-4cbf-88b0-5427a731ba7d@linaro.org> On Mon, Jan 19, 2026 at 12:35:23PM +0000, James Clark wrote: [...] > > @@ -28,7 +28,7 @@ config STM_PROTO_BASIC > > config STM_PROTO_SYS_T > > tristate "MIPI SyS-T STM framing protocol driver" > > - default CONFIG_STM > > + default STM > > The help below here says "If you don't know what this is, say N." which > makes me wonder if this should be on by default or not? STM_PROTO_BASIC is a must have config when enabling STM. While STM_PROTO_SYS_T is not mandatory, but it is useful to build it so that users can select the protocol dynamically at runtime. > Also everything is in an "if STM" block, so "default STM" is a bit > redundant. It's not that obvious what the intention was. They are two different things. "if STM" expresses a dependency (the module depends on STM), while "default STM" means the module will be selected by default if STM is enabled. Thanks, Leo P.s. I also tried using the "select" and "imply" syntax to enable the protocol configurations. Based on testing, I did not observe any difference compared to using the "default" syntax.