Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3004900yba; Tue, 16 Apr 2019 02:35:56 -0700 (PDT) X-Google-Smtp-Source: APXvYqwZgoyp0GQx1gHq8sCsJBcOI7+Cw4zDduNNo2T5DVKEQNiaFAOFA8CK1+kaNANmNm5nw+GX X-Received: by 2002:a65:64c9:: with SMTP id t9mr74752830pgv.221.1555407356433; Tue, 16 Apr 2019 02:35:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555407356; cv=none; d=google.com; s=arc-20160816; b=JiyUuMU/33raiO5yRIJfrGum0gprw1pm26TnSZxoLMhFLOPKQg/FuGh2gSfMdqjDUr 2Ucro5nD5nfMzMKqQ6qsyNPAWopHslf6iYh9AIZDQnfGbwrS72pZ7TmHFIgSjE1vi0MD tWD6TyTVjY4cQq2DpcNWsIY8kJRPfE+HB1seuwCQRWG8X6CXdUtzKom3Vd60QoSpwlYd 2fsO1TgMCBKtn6B1r90pCIE75b2UwdbBjltOY+TiVMmrHVkO1JPkP5F3qvQ6zS9WNHtw hBUITSKntW8nlxxi57jPagZiB5CXkBteyNQgkkMErBBZK260h+dpz/R0ovDytMEMdapT oJ4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=y8SYaGoutdfOHJIn+M34UOLRTBJ+A8CNHt0COhnf/qI=; b=PAaGPXAsR/W5NhmwqSi83BJe+JH0zl+Gq3M3E3Rv46SG6kpMF/TsJBI1jEi+bQFy3s u+kvc1hQzE772k6peVEKl6C7hOSHcMEEadCGzMKwyCOTYKMW9tFgUB7RQApY6nC2dT75 ZKQ8oZVZzR/8pJ/bYPeEtxW4oG12EhMWH4aq4l+cWIv9VJzyuIARuoVfbK/bozYXynlt SlXCE9JrBTE9XeiTl7dgsHXqL9qhalqd8x5KZNBZPUw6ZuLFjg1fJTLVL2QPMo7HnwT/ j/ujya72lODwdInHVcWqap23V/YO6BeWQaJ/AY6iraui6BC/PVqM3O7T1P1HZRg99J/R pmSA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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. [209.132.180.67]) by mx.google.com with ESMTP id 144si21821414pgf.59.2019.04.16.02.35.40; Tue, 16 Apr 2019 02:35:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 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 S1728972AbfDPJe7 (ORCPT + 99 others); Tue, 16 Apr 2019 05:34:59 -0400 Received: from mga07.intel.com ([134.134.136.100]:12912 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726739AbfDPJe7 (ORCPT ); Tue, 16 Apr 2019 05:34:59 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Apr 2019 02:34:58 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,357,1549958400"; d="scan'208";a="165154947" Received: from lahna.fi.intel.com (HELO lahna) ([10.237.72.157]) by fmsmga001.fm.intel.com with SMTP; 16 Apr 2019 02:34:55 -0700 Received: by lahna (sSMTP sendmail emulation); Tue, 16 Apr 2019 12:34:54 +0300 Date: Tue, 16 Apr 2019 12:34:54 +0300 From: Mika Westerberg To: Gaurav Kohli Cc: Srinivas Kandagatla , gregkh@linuxfoundation.org, maxime.ripard@bootlin.com, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvmem: core: add NVMEM_SYSFS Kconfig Message-ID: <20190416093454.GN2654@lahna.fi.intel.com> References: <20190415164011.2638-1-srinivas.kandagatla@linaro.org> <3a66797d-347d-2414-14e1-edbcd7c39ae8@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3a66797d-347d-2414-14e1-edbcd7c39ae8@codeaurora.org> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 16, 2019 at 10:49:22AM +0530, Gaurav Kohli wrote: > Hi Srinivas, > > Thanks for the patch, > By default NVMEM_SYSFS should be set true, those whose don't want they can > disable the same. > > If we go with disable option, there are chances of eeprom may break in below > case: > > if (config->compat) { > rval = nvmem_sysfs_setup_compat(nvmem, config); -> this will > return error as config is disabled. > if (rval) > goto err_device_del; > } I also think this may cause problems with Thunderbolt devices because the upgradeable NVM is exposed to the userspace via these sysfs files and those are being used by fwupd. If the files disappear it makes NVM upgrade somewhat harder ;-) At least it would be good to include following as part of this series if you plan to disable the sysfs entries by default: diff --git a/drivers/thunderbolt/Kconfig b/drivers/thunderbolt/Kconfig index f4869c38c7e4..dd5facab0af2 100644 --- a/drivers/thunderbolt/Kconfig +++ b/drivers/thunderbolt/Kconfig @@ -7,6 +7,7 @@ menuconfig THUNDERBOLT select CRYPTO select CRYPTO_HASH select NVMEM + select NVMEM_SYSFS help Thunderbolt Controller driver. This driver is required if you want to hotplug Thunderbolt devices on Apple hardware or on PCs