From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69CCFC4321D for ; Tue, 21 Aug 2018 14:33:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 25E112170E for ; Tue, 21 Aug 2018 14:33:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=linaro.org header.i=@linaro.org header.b="kDynzjNq" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 25E112170E Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linaro.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727752AbeHURxu (ORCPT ); Tue, 21 Aug 2018 13:53:50 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:36198 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726743AbeHURxu (ORCPT ); Tue, 21 Aug 2018 13:53:50 -0400 Received: by mail-wm0-f66.google.com with SMTP id w24-v6so3069775wmc.1 for ; Tue, 21 Aug 2018 07:33:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Un0w2l7Yz8T6CyGn0WzV6GbAnHWwvbXDyMP7AeR90UY=; b=kDynzjNqnZqV0md5ttV4QDdm0w93XJr/VkOUMCR4dSVJ68VzLYtYjXLcRz/dqiRa/1 CmW4UaesVjLNQuZICnuhBegUiaOgBKHKWXV8ZPWRbKUGwNwIVQH/RcB10dY/y3/BsAUN iZ0VrVemaUGebFdPpNIbn9avj56bv7+N226G0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Un0w2l7Yz8T6CyGn0WzV6GbAnHWwvbXDyMP7AeR90UY=; b=RN+U/7c7lvzXh87NpIofItPbnQupZJvXAJzc/0pEXuqCNF/BBmkO8riej6181BlYXH YtyWr9q/1afvTl9yEfX9JaLzuHlye90VMF1ZmP4znhxc+gsFsx/vHHsYeP/Hd0GFRXfM GkcAbdijO9WpBSl+2btFbjABIKf0ozVmkAfbgfYjCfM8OGzjxHvHaPUktbHF9CmdCyOp /g/XiAl2ppLgbmfO8kPhQqB7rEAKDYS+Qw29J78JNkU0U41C5TD6MX1Q9jrquYOzLBjJ q3EN6kU+YQUi0B9aTljni9325WfbJvxqCtBSfIJfkePXy9sFThxFHzCyGnTlANnbtjIU 7WSg== X-Gm-Message-State: APzg51Bxpx4/RCP9r6M7WKh/32UvBXBbKSrJZPyyMeGXtrXzKO1bZ4Wa 0AJp86JU0/j2wcW1tfyzBQRUow== X-Google-Smtp-Source: ANB0VdZYxg5SrQ3btL4IdeDF1brUb50wZSwWIFF/N+DARcii3DYrm1omOy8+220M6LzUn1HUMf7mMg== X-Received: by 2002:a1c:9744:: with SMTP id z65-v6mr1274632wmd.105.1534862005042; Tue, 21 Aug 2018 07:33:25 -0700 (PDT) Received: from [192.168.0.18] (cpc90716-aztw32-2-0-cust92.18-1.cable.virginm.net. [86.26.100.93]) by smtp.googlemail.com with ESMTPSA id g2-v6sm1880072wme.20.2018.08.21.07.33.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Aug 2018 07:33:24 -0700 (PDT) Subject: Re: [PATCH v2 06/29] mtd: Add support for reading MTD devices via the nvmem API To: Boris Brezillon , Alban Cc: Bartosz Golaszewski , Jonathan Corbet , Sekhar Nori , Kevin Hilman , Russell King , Arnd Bergmann , Greg Kroah-Hartman , David Woodhouse , Brian Norris , Marek Vasut , Richard Weinberger , Grygorii Strashko , "David S . Miller" , Naren , Mauro Carvalho Chehab , Andrew Morton , Lukas Wunner , Dan Carpenter , Florian Fainelli , Ivan Khoronzhuk , Sven Van Asbroeck , Paolo Abeni , Rob Herring , David Lechner , Andrew Lunn , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org, linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org, netdev@vger.kernel.org, Bartosz Golaszewski References: <20180810080526.27207-1-brgl@bgdev.pl> <20180810080526.27207-7-brgl@bgdev.pl> <20180817182720.6a6e5e8e@bbrezillon> <20180819133106.0420df5f@tock> <20180819184609.6dcdbb9a@bbrezillon> <20180821005327.0d312a85@tock> <20180821074404.23aaeb6b@bbrezillon> <20180821142716.0adcdd56@eos> <20180821145725.3b385399@bbrezillon> <20180821155706.2adf3b4c@eos> <20180821162644.5a1d7799@bbrezillon> From: Srinivas Kandagatla Message-ID: <2d5761f4-2c27-5a23-a635-9205124c993a@linaro.org> Date: Tue, 21 Aug 2018 15:33:22 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20180821162644.5a1d7799@bbrezillon> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 21/08/18 15:26, Boris Brezillon wrote: >> This also has the side effect that nvmem cells defined in DT don't >> appear in sysfs, unlike those defined from board code. > Wow, that's not good. I guess we'll want to make that consistent at > some point. > support for sysfs entries per cell is not available in nvmem. However there is nvmem sysfs entry per provider which can be read by the user space if required. --srini