1. 27 Sep, 2020 8 commits
  2. 25 Sep, 2020 1 commit
  3. 24 Sep, 2020 2 commits
    • Jon Hunter's avatar
      dt-bindings: eeprom: at24: Add label property for AT24 · 412b7a52
      Jon Hunter authored
      Add a label property for the AT24 EEPROM to allow a custom name to be
      used for identifying the EEPROM on a board. This is useful when there
      is more than one EEPROM present.
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Reviewed-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarBartosz Golaszewski <bgolaszewski@baylibre.com>
      412b7a52
    • Jon Hunter's avatar
      eeprom: at24: Initialise AT24 NVMEM ID field · f434f9b7
      Jon Hunter authored
      The AT24 EEPROM driver does not initialise the 'id' field of the
      nvmem_config structure and because the entire structure is not
      initialised, it ends up with a random value. This causes the NVMEM
      driver to append the device 'devid' value to name of the NVMEM
      device. Ideally for I2C devices such as the AT24 that already have a
      unique name, we would not bother to append the 'devid'. However, given
      that this has always been done for AT24 devices, we cannot remove the
      'devid' as this will change the name of the userspace sysfs node for
      the NVMEM device. Nonetheless we should ensure that the 'id' field of
      the nvmem_config structure is initialised so that there is no chance of
      a random value causes problems in the future. Therefore, set the NVMEM
      config.id to NVMEM_DEVID_AUTO for AT24 EEPROMs so that the 'devid' is
      always appended.
      Signed-off-by: default avatarJon Hunter <jonathanh@nvidia.com>
      Signed-off-by: default avatarBartosz Golaszewski <bgolaszewski@baylibre.com>
      f434f9b7
  4. 21 Sep, 2020 13 commits
  5. 18 Sep, 2020 7 commits
  6. 17 Sep, 2020 1 commit
  7. 09 Sep, 2020 4 commits
  8. 28 Aug, 2020 4 commits