From: Divagar Mohandass <divagar.mohandass@intel.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, wsa@the-dreams.de,
sakari.ailus@iki.fi
Cc: devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, rajmohan.mani@intel.com,
Divagar Mohandass <divagar.mohandass@intel.com>
Subject: [PATCH v4 1/3] dt-bindings: add eeprom "size" property
Date: Wed, 30 Aug 2017 22:35:38 +0530 [thread overview]
Message-ID: <1504112740-14072-2-git-send-email-divagar.mohandass@intel.com> (raw)
In-Reply-To: <1504112740-14072-1-git-send-email-divagar.mohandass@intel.com>
This adds eeprom "size" as optional property for i2c eeproms.
The "size" property allows explicitly specifying the size of the
EEPROM chip in bytes.
Signed-off-by: Divagar Mohandass <divagar.mohandass@intel.com>
---
Documentation/devicetree/bindings/eeprom/eeprom.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/eeprom/eeprom.txt b/Documentation/devicetree/bindings/eeprom/eeprom.txt
index 5696eb5..1436569 100644
--- a/Documentation/devicetree/bindings/eeprom/eeprom.txt
+++ b/Documentation/devicetree/bindings/eeprom/eeprom.txt
@@ -32,6 +32,8 @@ Optional properties:
- read-only: this parameterless property disables writes to the eeprom
+ - size: total eeprom size in bytes
+
Example:
eeprom@52 {
--
1.9.1
next prev parent reply other threads:[~2017-08-30 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 17:05 [PATCH v4 0/3] enable eeprom "size" property and runtime pm Divagar Mohandass
2017-08-30 17:05 ` Divagar Mohandass [this message]
2017-08-31 15:26 ` [PATCH v4 1/3] dt-bindings: add eeprom "size" property Rob Herring
2017-09-01 12:02 ` Mohandass, Divagar
2017-08-30 17:05 ` [PATCH v4 2/3] eeprom: at24: add support to fetch eeprom device property "size" Divagar Mohandass
2017-08-30 17:05 ` [PATCH v4 3/3] eeprom: at24: enable runtime pm support Divagar Mohandass
2017-08-30 21:19 ` Sakari Ailus
2017-08-31 11:24 ` Mohandass, Divagar
2017-08-31 15:37 ` Sakari Ailus
2017-09-01 18:26 ` Mohandass, Divagar
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=1504112740-14072-2-git-send-email-divagar.mohandass@intel.com \
--to=divagar.mohandass@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rajmohan.mani@intel.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
--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
all inboxes | Powered by JetHome®