Skip to content
Snippets Groups Projects
  1. Nov 04, 2022
  2. Oct 24, 2022
    • Vaibhav Gupta's avatar
      fmc-eeprom: Use "nvmem_device_find()" to get nvmem device · 756b511b
      Vaibhav Gupta authored
      
      To use "nvmem_device_get()" we need to find correct name of our nvmem
      device, which is a very complex job than it seems.
      
      The way nvmem-consumer framework is designed, we only have the info
      about the parent device which is handled by i2c. Thus, there is no
      non-hackish way we can get the name of our nvmem-device.
      
      One pattern which is helpful is that the nvmem framework names its
      devices by just appending an id to the name of the parent device. So,
      if the parent device is "2-0050", the nvmem device will be 2-005<id>.
      
      The silver lining in our case is that as per FMC standard, we have only
      one eeprom/nvmem device per i2c handler. Thus, we just need to check
      that out of all nvmem devices, which one contains the name of our
      i2c handler.
      
      Signed-off-by: default avatarVaibhav Gupta <vaibhav.gupta@cern.ch>
      756b511b
    • Vaibhav Gupta's avatar
      drivers: fmc: eeprom: Improve error checking · 0e8dd7d8
      Vaibhav Gupta authored
      
      nvmem_device_get() may return an error pointed instead of NULL, thus
      check for it.
      
      Picked from the changes done by Mathis Marion for Oscimp-WRTD project.
      
      Signed-off-by: default avatarVaibhav Gupta <vaibhav.gupta@cern.ch>
      0e8dd7d8
    • Dimitris Lampridis's avatar
      Support Kernel version 5.10.65 · f48aded1
      Dimitris Lampridis authored
      
      Update APIs wherever needed to supposrt linux v5.10.65 as well.
      
      Signed-off-by: default avatarVaibhav Gupta <vaibhav.gupta@cern.ch>
      f48aded1
  3. Feb 23, 2022
  4. Jul 29, 2021
  5. Nov 26, 2020
  6. Oct 20, 2020
  7. Sep 18, 2019
  8. Sep 09, 2019