Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D0A9EC636D6 for ; Tue, 7 Feb 2023 14:06:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231864AbjBGOGD (ORCPT ); Tue, 7 Feb 2023 09:06:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49078 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231326AbjBGOF6 (ORCPT ); Tue, 7 Feb 2023 09:05:58 -0500 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B6B0CD53E; Tue, 7 Feb 2023 06:05:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1675778743; x=1707314743; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=mkEL9K9dbw3j0hR5Y0jMzBAGrvZ+x1Pz9OzilWESy/k=; b=lhdnwGV5N4tN6jQskw3C3gYcKKySQAacO5H9O1J9Bu+U010T2te1xTld Fspmtpbex1Uo8QLlmsupEzlHFBhAjHCqPuNrikIbz3f6h1v1fOcSIdr0I b4V1rcQTDkcdW3LHmMs0gyCd1CXD4HsetyPWMAKMOAD5OTot63l3Nguhu mP8eVfET2SZAqchyG4PYgOlDr+6x1o7qfLUeP+XAsGFALrHNzyz/CgE0m VUhGymBLLr7UrYVAVFRFpX18+0stFL/RpT6z0cydix/YI8MqhXuYOxRLz L+t4dcNHL8GxVny9GNmHuIDeJs3XwnVnWlDxYwEimg4GjI4hr37jcMjGP A==; X-IronPort-AV: E=McAfee;i="6500,9779,10614"; a="329529775" X-IronPort-AV: E=Sophos;i="5.97,278,1669104000"; d="scan'208";a="329529775" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Feb 2023 06:02:44 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10614"; a="730440011" X-IronPort-AV: E=Sophos;i="5.97,278,1669104000"; d="scan'208";a="730440011" Received: from black.fi.intel.com ([10.237.72.28]) by fmsmga008.fm.intel.com with ESMTP; 07 Feb 2023 06:02:42 -0800 Received: by black.fi.intel.com (Postfix, from userid 1001) id B34E21C5; Tue, 7 Feb 2023 16:03:20 +0200 (EET) Date: Tue, 7 Feb 2023 16:03:20 +0200 From: Mika Westerberg To: Michael Walle Cc: mauro.lima@eclypsium.com, broonie@kernel.org, linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org Subject: Re: [PATCH 1/1] spi: intel: Remove DANGEROUS tag from pci driver Message-ID: References: <20230206183143.75274-2-mauro.lima@eclypsium.com> <20230207135254.2465816-1-michael@walle.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230207135254.2465816-1-michael@walle.cc> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Tue, Feb 07, 2023 at 02:52:54PM +0100, Michael Walle wrote: > > Modern CPUs exposes this controller as PCI device that only uses > > hardware sequencing capabilities which is safer than software > > sequencing. > > Leave the platform driver as *DANGEROUS* and update help text since > > most of these controllers are using software sequencing. > > Out of curiosity, what is hardware sequencing? Maybe this should > be explained a bit more in the Kconfig help text. Looks like the > dangerous was there because you can update the bios and that > could eventually lead to a bricked mainboard. So hardware > sequencing helps there? how? Hardware sequencing means the controller exposes just a bunch of "high level" operations to the software. Such as read, write, erase and so on but does not allow running the actual "low level" SPI-NOR opcodes. Software sequencing on the other hand allows running pretty much any opcode and this is what caused problems for certain Lenovo laptops few years back that then resulted adding DANGEROUS to the Kconfig. Typically the flash is locked by the BIOS so ordinary users cannot really overwrite it, even by accident.