Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp2041434pxa; Mon, 3 Aug 2020 06:07:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzOpGs7djDSrlS65M+WPEZEkX8iZEhIIKnT3ni08oFOFCwi721G19vHM0g9BWG7GA+8SQpM X-Received: by 2002:a17:906:551:: with SMTP id k17mr6866108eja.322.1596460021996; Mon, 03 Aug 2020 06:07:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596460021; cv=none; d=google.com; s=arc-20160816; b=j9G8rVJYtztLIokO8wPOPs1Gbs3cG+cPbHdLPNH3yZuw6gmv2sRkvSOCsBW1f2S5vO grZKjnpqRIkL6MMB0PeACVhMk7ElNMVoYWknyuy4eyXNbNdOq0/O6u/LkxaypHxWC9Yh GCUywtyuMaxUa3S3x04ZFeFfFvBIGiJyyXLlH/P7b7292x468sSfWGnd6pgjkWV07mNO 6I7H0YLqfEdX8JaKdFr13mztS6ZojMZ7LD6kgqEIOFH4+Xw1+7oo42oTk8J9piyqEKjT TbmgTzB/OvhzgJ3Su+u5/4y3OEikkLVuJg5H12yATs1+WRQtZ7C2CoBE5CewWE28qeli k1ag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:ironport-sdr:ironport-sdr; bh=i4CB47tEb+RyuggjcAQnE5Ps8dCK2GBWkag9hsHsQdI=; b=QPaAtUrkIFi+jsoAETaPnyQ8Gx3uJTwku2v5cD5nP/+i+a4UAZB1zbKjbpPbYfk4yq o3e72irvEF0bNIlAesxRlVO2zA/Ab0pBJ0nBB++pAS6vZb55ehd8qmyeMtM3vYCxXYDv /vW2K/wKjf87feYyzdQtkjX5uTIx8muKyQbSjU5QjYbLFiZ6+O6UVMubuoMHRNNE9idg hhcUsOch85o7QSQhvxzIpTNVDYJeZMcr473SCk0VbENV/UJCvfTwRLh+NXRB2cHTaRr8 vLzoCH2Kx7mlIPRrQ4yv6H/L++raY2fMrB8TS41ZB7XRXA0it+4wVUz5inwTCKdwGJl4 qq+Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w4si3154957ejb.443.2020.08.03.06.06.37; Mon, 03 Aug 2020 06:07:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726766AbgHCNFq (ORCPT + 99 others); Mon, 3 Aug 2020 09:05:46 -0400 Received: from mga14.intel.com ([192.55.52.115]:7003 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726118AbgHCNFp (ORCPT ); Mon, 3 Aug 2020 09:05:45 -0400 IronPort-SDR: teQvRFCIq5uN5KuOH1Z1cfaI7yUY1J88mfKwESrIAKlMZNIzTn3Q/bA3nyT5uFEXhcbGg3uvp8 46n67bx8nX2g== X-IronPort-AV: E=McAfee;i="6000,8403,9701"; a="151301958" X-IronPort-AV: E=Sophos;i="5.75,430,1589266800"; d="scan'208";a="151301958" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Aug 2020 06:05:37 -0700 IronPort-SDR: 97bGbyL6YMQTKXS8v/uAnE7kejawVmtdJ7xUNwRv4412nrgH29Uv0FezDr/4/nZGZWddQ6sQa6 TUAzMI00e65A== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,430,1589266800"; d="scan'208";a="396051205" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.163]) by fmsmga001.fm.intel.com with SMTP; 03 Aug 2020 06:05:33 -0700 Received: by lahna (sSMTP sendmail emulation); Mon, 03 Aug 2020 16:05:32 +0300 Date: Mon, 3 Aug 2020 16:05:32 +0300 From: Mika Westerberg To: Daniel Gutson Cc: Richard Hughes , Tudor Ambarus , Miquel Raynal , Richard Weinberger , Vignesh Raghavendra , Boris Brezillon , linux-mtd , linux-kernel , Alex Bazhaniuk , Arnd Bergmann , Greg Kroah-Hartman Subject: Re: [PATCH] Module argument to control whether intel-spi-pci attempts to turn the SPI flash chip writeable Message-ID: <20200803130532.GY1375436@lahna.fi.intel.com> References: <20200724212853.11601-1-daniel.gutson@eclypsium.com> <20200803095720.GC1375436@lahna.fi.intel.com> <20200803102711.GK1375436@lahna.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 03, 2020 at 09:58:23AM -0300, Daniel Gutson wrote: > On Mon, Aug 3, 2020 at 7:27 AM Mika Westerberg > wrote: > > > > On Mon, Aug 03, 2020 at 11:18:12AM +0100, Richard Hughes wrote: > > > On Mon, 3 Aug 2020 at 10:57, Mika Westerberg > > > wrote: > > > > I think instead of this we should simply make it so that the driver > > > > never tries to make the chip writable. > > > > > > I think this is a good idea, but I wasn't sure if it was an acceptable > > > behaviour change. Should the driver still try to set BCR_WPD when > > > writing an image (i.e. defer the setting of write enable until later), > > > or just not set the BCR register at all? I think your last comment was > > > the latter, but wanted to check. > > > > I would say not set it at all. I think it was (my) mistake to set it in > > the first place. > > Do you want me to remove the module parameter from intel-spi too and > do the same? No, I think that should still be left there. Then by default it is read-only and you can only enable writing if the BIOS allows it and that the user actually requested it.