HI Robert and Heiko, po 28. 10. 2019 v 19:32 odesÃlatel Robert Beckett <bob.beck...@collabora.com> napsal: > > Add ability to specify paritions for eeprom in device tree, and query > eeprom device sizes. > Each partition creates a child device, allowing board code to > find the eeprom parition by name. > > > Robert Beckett (2): > misc: i2c_eeprom: add fixed partitions support > misc: i2c_eeprom: add size query > > drivers/misc/i2c_eeprom.c | 243 +++++++++++++++++++++++++++++++++++--- > include/i2c_eeprom.h | 12 ++ > 2 files changed, 236 insertions(+), 19 deletions(-)
What's the recommended way to work with i2c_eeprom_partitions? I have them probed but curious how I should work with them. i2c 1 [ + ] i2c_mux_bus_drv | | |-- i2c@ff030000->i2c-mux@74->i2c@0 i2c_eeprom 0 [ + ] i2c_eeprom | | | `-- eeprom@54 i2c_eeprom 1 [ ] i2c_eeprom_partition | | | |-- board-sn@0 i2c_eeprom 2 [ ] i2c_eeprom_partition | | | |-- eth-mac@20 i2c_eeprom 3 [ ] i2c_eeprom_partition | | | |-- board-name@d0 i2c_eeprom 4 [ ] i2c_eeprom_partition | | | `-- board-revision@e0 Is there any u-boot command for reading values from these partitions? Or are you just referencing them by fdt_path_offset/uclass_get_device_by_of_offset? Thanks, Michal -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs