From: Rob Herring <robh@kernel.org>
To: Khouloud Touil <ktouil@baylibre.com>
Cc: bgolaszewski@baylibre.com, robh+dt@kernel.org,
mark.rutland@arm.com, srinivas.kandagatla@linaro.org,
baylibre-upstreaming@groups.io, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
linus.walleij@linaro.org, Khouloud Touil <ktouil@baylibre.com>
Subject: Re: [PATCH v4 1/5] dt-bindings: nvmem: new optional property wp-gpios
Date: Wed, 8 Jan 2020 14:54:01 -0600 [thread overview]
Message-ID: <20200108205401.GA15674@bogus> (raw)
In-Reply-To: <20200107092922.18408-2-ktouil@baylibre.com>
On Tue, 7 Jan 2020 10:29:18 +0100, 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 <ktouil@baylibre.com>
> ---
> Documentation/devicetree/bindings/nvmem/nvmem.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-01-08 20:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 9:29 [PATCH v4 0/5] at24: move write-protect pin handling to nvmem core Khouloud Touil
2020-01-07 9:29 ` [PATCH v4 1/5] dt-bindings: nvmem: new optional property wp-gpios Khouloud Touil
2020-01-07 9:50 ` Linus Walleij
2020-01-08 20:54 ` Rob Herring [this message]
2020-01-07 9:29 ` [PATCH v4 2/5] nvmem: add support for the write-protect pin Khouloud Touil
2020-01-30 8:06 ` Geert Uytterhoeven
2020-02-17 13:14 ` Khouloud Touil
2020-02-17 14:34 ` Bartosz Golaszewski
2020-02-17 15:11 ` Geert Uytterhoeven
2020-01-07 9:29 ` [PATCH v4 3/5] dt-bindings: at24: make wp-gpios a reference to the property defined by nvmem Khouloud Touil
2020-01-08 20:54 ` Rob Herring
2020-01-07 9:29 ` [PATCH v4 4/5] dt-bindings: at25: add reference for the wp-gpios property Khouloud Touil
2020-01-08 20:54 ` Rob Herring
2020-01-09 9:47 ` Bartosz Golaszewski
2020-01-14 14:42 ` Greg KH
2020-01-14 15:05 ` Bartosz Golaszewski
2020-01-07 9:29 ` [PATCH v4 5/5] eeprom: at24: remove the write-protect pin support Khouloud Touil
2020-01-09 10:31 ` [PATCH v4 0/5] at24: move write-protect pin handling to nvmem core Bartosz Golaszewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200108205401.GA15674@bogus \
--to=robh@kernel.org \
--cc=baylibre-upstreaming@groups.io \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ktouil@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox