From: Sven Van Asbroeck <svendev@arcx.com>
To: svendev@arcx.com, robh+dt@kernel.org, mark.rutland@arm.com,
wsa@the-dreams.de, brgl@bgdev.pl, nsekhar@ti.com,
sakari.ailus@linux.intel.com, david@lechnology.com,
javier@dowhile0.org, divagar.mohandass@intel.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: [PATCH v4 2/2] dt-bindings: add eeprom "at24,no-read-rollover" property
Date: Tue, 5 Dec 2017 10:23:42 -0500 [thread overview]
Message-ID: <1512487422-6284-3-git-send-email-svendev@arcx.com> (raw)
In-Reply-To: <1512487422-6284-1-git-send-email-svendev@arcx.com>
Adds an optional property for at24 eeproms.
This parameterless property indicates that the multi-address eeprom
does not automatically roll over reads to the next slave address.
Signed-off-by: Sven Van Asbroeck <svendev@arcx.com>
---
Documentation/devicetree/bindings/eeprom/eeprom.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/eeprom/eeprom.txt b/Documentation/devicetree/bindings/eeprom/eeprom.txt
index 27f2bc1..5bfc0ac 100644
--- a/Documentation/devicetree/bindings/eeprom/eeprom.txt
+++ b/Documentation/devicetree/bindings/eeprom/eeprom.txt
@@ -38,6 +38,11 @@ Optional properties:
- size: total eeprom size in bytes
+ - at24,no-read-rollover:
+ This parameterless property indicates that the multi-address
+ eeprom does not automatically roll over reads to the next
+ slave address. Please consult the manual of your device.
+
Example:
eeprom@52 {
--
1.9.1
next prev parent reply other threads:[~2017-12-05 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 15:23 [PATCH v4 0/2] at24: support eeproms that do not auto-rollover reads Sven Van Asbroeck
2017-12-05 15:23 ` [PATCH v4 1/2] " Sven Van Asbroeck
2017-12-05 15:23 ` Sven Van Asbroeck [this message]
2017-12-06 22:04 ` [PATCH v4 2/2] dt-bindings: add eeprom "at24,no-read-rollover" property Rob Herring
2017-12-07 14:06 ` Sven Van Asbroeck
2017-12-07 14:21 ` 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=1512487422-6284-3-git-send-email-svendev@arcx.com \
--to=svendev@arcx.com \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=divagar.mohandass@intel.com \
--cc=javier@dowhile0.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=wsa@the-dreams.de \
/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).