lkml.org 
[lkml]   [2015]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v4 05/10] eeprom: Add bindings for simple eeprom framework
    Date
    This patch adds bindings for simple eeprom framework which allows eeprom
    consumers to talk to eeprom providers to get access to eeprom cell data.

    Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
    [Maxime Ripard: intial version of eeprom framework]
    Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
    ---
    .../devicetree/bindings/eeprom/eeprom.txt | 58 ++++++++++++++++++++++
    1 file changed, 58 insertions(+)
    create mode 100644 Documentation/devicetree/bindings/eeprom/eeprom.txt

    diff --git a/Documentation/devicetree/bindings/eeprom/eeprom.txt b/Documentation/devicetree/bindings/eeprom/eeprom.txt
    new file mode 100644
    index 0000000..fb71d46
    --- /dev/null
    +++ b/Documentation/devicetree/bindings/eeprom/eeprom.txt
    @@ -0,0 +1,58 @@
    += EEPROM Data Device Tree Bindings =
    +
    +This binding is intended to represent the location of hardware
    +configuration data stored in EEPROMs.
    +
    +On a significant proportion of boards, the manufacturer has stored
    +some data on an EEPROM-like device, for the OS to be able to retrieve
    +these information and act upon it. Obviously, the OS has to know
    +about where to retrieve these data from, and where they are stored on
    +the storage device.
    +
    +This document is here to document this.
    +
    += Data providers =
    +Contains bindings specific to provider drivers and data cells as children
    +to this node.
    +
    += Data cells =
    +These are the child nodes of the provider which contain data cell
    +information like offset and size in eeprom provider.
    +
    +Required properties:
    +reg: specifies the offset in byte within that storage device, and the length
    + in bytes of the data we care about.
    + There could be more then one offset-length pairs in this property.
    +
    +Optional properties:
    +As required by specific data parsers/interpreters.
    +
    +For example:
    +
    + /* Provider */
    + qfprom: qfprom@00700000 {
    + compatible = "qcom,qfprom";
    + reg = <0x00700000 0x8000>;
    + ...
    +
    + /* Data cells */
    + tsens_calibration: calib@4404 {
    + reg = <0x4404 0x10>;
    + };
    +
    + serial_number: sn {
    + reg = <0x104 0x4>, <0x204 0x4>, <0x30c 0x4>;
    +
    + };
    + ...
    + };
    +
    += Data consumers =
    +Are device nodes which consume eeprom data cells.
    +
    +For example:
    +
    + tsens {
    + ...
    + calibration = <&tsens_calibration>;
    + };
    --
    1.9.1


    \
     
     \ /
      Last update: 2015-03-31 00:41    [W:4.043 / U:0.292 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site