From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Peter Rosin <peda@axentia.se>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PATCH v2 0/2] eeprom: at24: write-protect pin support
Date: Wed, 20 Dec 2017 09:26:31 +0100 [thread overview]
Message-ID: <20171220082633.32237-1-brgl@bgdev.pl> (raw)
AT24 EEPROMs have a write-protect pin, which - when pulled high -
inhibits writes to the upper quadrant of memory (although it has been
observed that on some chips it disables writing to the entire memory
range).
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. On linux this means that we either need to hog the line all
the time, or set the GPIO value before writing from outside of the
at24 driver.
This series adds support for the write-protect pin split into two
parts. The first patch extends the relevant binding document, while
the second modifies the at24 code to pull the write-protect GPIO
low (if present) during write operations.
v1 -> v2:
- renamed the DT property to wp-gpios
Bartosz Golaszewski (2):
dt-bindings: at24: new optional property - wp-gpios
eeprom: at24: add support for the write-protect pin
Documentation/devicetree/bindings/eeprom/at24.txt | 3 +++
drivers/misc/eeprom/at24.c | 11 +++++++++++
2 files changed, 14 insertions(+)
--
2.15.1
next reply other threads:[~2017-12-20 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 8:26 Bartosz Golaszewski [this message]
2017-12-20 8:26 ` [PATCH v2 1/2] dt-bindings: at24: new optional property - wp-gpios Bartosz Golaszewski
[not found] ` <20171220082633.32237-2-brgl-ARrdPY/1zhM@public.gmane.org>
2017-12-20 21:48 ` Rob Herring
2017-12-20 8:26 ` [PATCH v2 2/2] eeprom: at24: add support for the write-protect pin Bartosz Golaszewski
[not found] ` <20171220082633.32237-1-brgl-ARrdPY/1zhM@public.gmane.org>
2017-12-20 10:21 ` [PATCH v2 0/2] eeprom: at24: write-protect pin support Andy Shevchenko
[not found] ` <CAHp75VfCD=mXvvbMT6PtjhgRznqfOSX_8Y8K3Zr64oJTbKnPeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-20 12:41 ` Bartosz Golaszewski
2017-12-20 15:00 ` Andy Shevchenko
2017-12-20 15:05 ` 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=20171220082633.32237-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).