From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CDDF221CA0E; Thu, 26 Jun 2025 10:11:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750932680; cv=none; b=cTsiKu8fwX5IKjZ8bsaNPdE3PCxJ8C2Zh0r2l9xPLm6qDGea8+/p5YrugwVuzbZ29nIt9We+cV0dBJR4yjx3lUZGoam8PL1HLq5aKuajYSgfDPFWK8EupCttvsFvkB7/sFrfIj+kfAKntYnZcDSXLEJRPpXMepW7UgQYiv3idLU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750932680; c=relaxed/simple; bh=hk5xqBm8kcJRDQ/Tpz/eCbR4dHy273+yDFMPzSNURyg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=dSvEaxEaXCshRcz1Zlw7Hbh6BTU57yE31kA7yQtxAyMCgDp9QE4wz5c4sVMsfMIHPUeT+l6e/W7Io1SvmskMsm8sO788FpT8hxp2lqOElSIPNjBQ+tgSY3fJTnJdCOdFMeQdUsGwkSzNQCGbs6nHXnv2vN3kzNOb6LsVe/GZUYI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ha4LBTh+; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ha4LBTh+" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 53B53C4CEEB; Thu, 26 Jun 2025 10:11:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1750932680; bh=hk5xqBm8kcJRDQ/Tpz/eCbR4dHy273+yDFMPzSNURyg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ha4LBTh+lw+wR4M5R9ROgQmZ2LE1GHd2O6WtlAqkpSBlnoeG1H2Wo0Lqn0JOiZ3YM ZgaOnGSxc21WeJbCm5Ofp8+vZWwy8scQ1rzmvdd2G/h9INXD84c7irH/r+WG0qmcAC 39X4yF/gfjIFvHOgokN7L2XB3IWBsAHTeTdF5rvWn8H1HjsdVNayUPZtHcLKyV6RqL Dn/sqdIxDdvh27yL6wDTMB6t3UKKbBdEfCSoPoNxigstYB8VN01o4lsQiWy4YmXKs6 FqiY+LqLZ5h0XARdKKcioygv3yvnwzgLVrBKfihivMlVHllwwRTlLPw/6h5zCfNwj5 bo0Q6uGVDbUHQ== Received: from johan by xi.lan with local (Exim 4.97.1) (envelope-from ) id 1uUjZg-000000007ks-02Ya; Thu, 26 Jun 2025 12:11:20 +0200 Date: Thu, 26 Jun 2025 12:11:20 +0200 From: Johan Hovold To: Dmitry Baryshkov Cc: Bjorn Andersson , Maximilian Luz , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Ard Biesheuvel , Steev Klimaszewski , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-efi@vger.kernel.org, Dmitry Baryshkov , Konrad Dybcio Subject: Re: [PATCH v4 6/8] firmware: qcom: scm: add modparam to control QSEECOM enablement Message-ID: References: <20250625-more-qseecom-v4-0-aacca9306cee@oss.qualcomm.com> <20250625-more-qseecom-v4-6-aacca9306cee@oss.qualcomm.com> Precedence: bulk X-Mailing-List: linux-efi@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: <20250625-more-qseecom-v4-6-aacca9306cee@oss.qualcomm.com> On Wed, Jun 25, 2025 at 01:53:25AM +0300, Dmitry Baryshkov wrote: > From: Dmitry Baryshkov > > In preparation to enabling QSEECOM for the platforms rather than > individual machines provide a mechanism for the user to override default > selection. Allow users to use qcom_scm.qseecom modparam. > > Setting it to 'force' will enable QSEECOM even if it disabled or not > handled by the allowlist. > > Setting it to 'off' will forcibly disable the QSEECOM interface, > allowing incompatible machines to function. > > Setting it to 'roefivars' will enable the QSEECOM interface, making UEFI > variables read-only. > > All other values mean 'auto', trusting the allowlist in the module. I don't see the need for this. The kernel should just provide sensible defaults. Johan