Skip to content

F
FMC Software Support
Switch branch/tag
  1. 07 Nov, 2022 3 commits
  3. 04 Nov, 2022 4 commits
  5. 02 Nov, 2022 2 commits
    • Vaibhav Gupta's avatar
      fmc-eeprom: Maintain the reference count of the device. · 59a48ab0
      Vaibhav Gupta authored 
      With nvmem framework, the reference counter of the nvmem device is
increased when we ask the device from the kernel via helper functions
like "nvmem_device_find()", "nvmem_device_get()", etc. If reference
count is zero, the driver can be unloaded (rmmod) during ongoing
operations.

Thus, the reference count should be incremented during add, and
decremented during delete.
Reported-by: Federico Vaga's avatarFederico Vaga <federico.vaga@cern.ch>
Signed-off-by: 's avatarVaibhav Gupta <vaibhav.gupta@cern.ch>
      59a48ab0
    • Vaibhav Gupta's avatar
      fmc-eeprom: Use "nvmem_device_find()" to get nvmem device · fe4f3dfc
      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-0050<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: 's avatarVaibhav Gupta <vaibhav.gupta@cern.ch>
      fe4f3dfc
  7. 07 Sep, 2022 1 commit
  9. 15 Aug, 2022 3 commits
  11. 26 Jul, 2022 2 commits
  13. 23 Feb, 2022 3 commits
  15. 29 Jul, 2021 4 commits
  17. 06 Jul, 2021 4 commits
  19. 10 Dec, 2020 4 commits
  21. 26 Nov, 2020 6 commits
  23. 26 Oct, 2020 4 commits