You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different EEPROM files are required to achieve best performance depending on the power amplifier (PA) and low noise amplifier (LNA) type which, as far as I understand, can be ePAeLNA, iPAiLNA, iPAeLNA or ePAiLNA, where e and i stand for internal and external respectively.
In case no EEPROM is available via NVMEM, we need to load the correct EEPROM file from the file system. So, provided, that there is no better way, we would probably need a property in device-tree to specify the PA/LNA type so that the fitting EEPROM file can be loaded.
The text was updated successfully, but these errors were encountered:
I had considered that but it will take precedence over NVMEM if I remember it correctly. For the use case where it is meant as a fallback in case NVMEM is damaged or missing, a behaviour that is the other way around is desirable.
Different EEPROM files are required to achieve best performance depending on the power amplifier (PA) and low noise amplifier (LNA) type which, as far as I understand, can be ePAeLNA, iPAiLNA, iPAeLNA or ePAiLNA, where e and i stand for internal and external respectively.
In case no EEPROM is available via NVMEM, we need to load the correct EEPROM file from the file system. So, provided, that there is no better way, we would probably need a property in device-tree to specify the PA/LNA type so that the fitting EEPROM file can be loaded.
The text was updated successfully, but these errors were encountered: