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=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=no 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 5C48EC33C9B for ; Tue, 7 Jan 2020 09:51:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 31F152077B for ; Tue, 7 Jan 2020 09:51:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="ESsRaSk7" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727675AbgAGJvC (ORCPT ); Tue, 7 Jan 2020 04:51:02 -0500 Received: from mail-lj1-f194.google.com ([209.85.208.194]:39012 "EHLO mail-lj1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726558AbgAGJvB (ORCPT ); Tue, 7 Jan 2020 04:51:01 -0500 Received: by mail-lj1-f194.google.com with SMTP id l2so54021826lja.6 for ; Tue, 07 Jan 2020 01:51:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7lwQwuwfM1iPF6iRTO0yd0IE/lAHtvYOS2zEBwR6gvo=; b=ESsRaSk7d2JY56/cgt/nXnrxJgfTupQnEmZZv8fV6TQ7hRK0Q5KWNLW//AWecNq6h9 Zuk595JfYWxqRW7TXSk1CndHashtdTijfRIWJPHdaW7xPsbvpTL1Y1BZ7Gn4nDMncf8+ nAedTzlJLdg1/g+osMgihw1mhBQCjIFs9LiyOoAkli5A6O4Qkzril5A2CpjkA3ciGwWl AkjWUcUerXOj01PMyJNuFVH5BIRcJY0KA5GIK296ubZhlxOff7rpN1nUxjHNyEc3C6hA L+xdcykZQbzzmTl3/zW9ddGJoYMGRGpcG3WeDSQiHSC5+31ioGivnMVPF7/M4v8utBug 0EvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7lwQwuwfM1iPF6iRTO0yd0IE/lAHtvYOS2zEBwR6gvo=; b=BbzSjYSul1H9GUHvyMkCQPbPbCFW7gr+uvzAQSRTBSPVnDKGbp7ROGkuJ2WOW8a1zs osx8NjlyOOHaHZbyxgkuYVNFXZHOA3vEY6UWHye/G5FlenmUYM3ohvYOX5wguwD6NM9p x+51/oY8YQ94al8OguV5BxWIxfkqwy3UMcS90BIPXBY2Yyp/6YU+Kew68YOO+oWf9Xst lCtUh+TL14siArb24uwUcllTsWHftSv5dolEYQHE5ZF6p8bpEe3OHCw0OyyWHqGOO1Mb +//OcIO2CgOWrmmNholpqte4akDNFBrrEfAjmvhlOT+Nx2H34912oa2vWf293hqR7SSW Dq+w== X-Gm-Message-State: APjAAAXNKEKLnJ8SNaT2KIxu1odNBQ299cVmhoIXBgcJQIuDYIiG01wp CcqACyado8uftkk3tK3aEUphYNWKh8oIWgXeInstjQ== X-Google-Smtp-Source: APXvYqylGF4/dGdkzkEMlIlEa1r7p28w7YxwevYK0M9wNzYKRMpP+8bfkSDdksAZIgT2FP8fUZHLxVLt/i4WOnPkXbU= X-Received: by 2002:a2e:9587:: with SMTP id w7mr60234687ljh.42.1578390659474; Tue, 07 Jan 2020 01:50:59 -0800 (PST) MIME-Version: 1.0 References: <20200107092922.18408-1-ktouil@baylibre.com> <20200107092922.18408-2-ktouil@baylibre.com> In-Reply-To: <20200107092922.18408-2-ktouil@baylibre.com> From: Linus Walleij Date: Tue, 7 Jan 2020 10:50:48 +0100 Message-ID: Subject: Re: [PATCH v4 1/5] dt-bindings: nvmem: new optional property wp-gpios To: Khouloud Touil Cc: Bartosz Golaszewski , Rob Herring , Mark Rutland , Srinivas Kandagatla , baylibre-upstreaming@groups.io, "linux-kernel@vger.kernel.org" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , linux-i2c Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 7, 2020 at 10:29 AM Khouloud Touil wrote: > Several memories have a write-protect pin, that when pulled high, it > blocks the write operation. > > On some boards, this pin is connected to a GPIO and pulled high by > default, which forces the user to manually change its state before > writing. > > Instead of modifying all the memory drivers to check this pin, make > the NVMEM subsystem check if the write-protect GPIO being passed > through the nvmem_config or defined in the device tree and pull it > low whenever writing to the memory. > > Add a new optional property to the device tree binding document, which > allows to specify the GPIO line to which the write-protect pin is > connected. > > Signed-off-by: Khouloud Touil Reviewed-by: Linus Walleij Yours, Linus Walleij