Commit e32a1f30 authored by Bartosz Golaszewski's avatar Bartosz Golaszewski

dt-bindings: at24: fix formatting and style

Make formatting and style consistent for the entire document.

This patch doesn't change the content of the binding.
Signed-off-by: default avatarBartosz Golaszewski <brgl@bgdev.pl>
Reviewed-by: default avatarJavier Martinez Canillas <javierm@redhat.com>
Reviewed-by: default avatarRob Herring <robh@kernel.org>
parent 6da28acf
...@@ -39,23 +39,23 @@ Required properties: ...@@ -39,23 +39,23 @@ Required properties:
"renesas,r1ex24002" - the fallback is "atmel,24c02" "renesas,r1ex24002" - the fallback is "atmel,24c02"
- reg : the I2C address of the EEPROM - reg: The I2C address of the EEPROM.
Optional properties: Optional properties:
- pagesize : the length of the pagesize for writing. Please consult the - pagesize: The length of the pagesize for writing. Please consult the
manual of your device, that value varies a lot. A wrong value manual of your device, that value varies a lot. A wrong value
may result in data loss! If not specified, a safety value of may result in data loss! If not specified, a safety value of
'1' is used which will be very slow. '1' is used which will be very slow.
- read-only: this parameterless property disables writes to the eeprom - read-only: This parameterless property disables writes to the eeprom.
- size: total eeprom size in bytes - size: Total eeprom size in bytes.
- no-read-rollover: - no-read-rollover: This parameterless property indicates that the
This parameterless property indicates that the multi-address multi-address eeprom does not automatically roll over
eeprom does not automatically roll over reads to the next reads to the next slave address. Please consult the
slave address. Please consult the manual of your device. manual of your device.
- wp-gpios: GPIO to which the write-protect pin of the chip is connected. - wp-gpios: GPIO to which the write-protect pin of the chip is connected.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment