Problem: FMC130 and FMC250 both have the same exactly exported functions for the Active Clock part (AD9510 and SI571), but the functions are reimplemented on both SMIOs. This makes it harder to maintain.
Also, client applications, such as the EPICS IOC, are forced to access the same functions with different service names, "FMC130M_4CH" and "FMC250M_4CH", instead of a generic name as "FMC_ACTIVE_CLOCK"
Solution: Split the active clock part into the "fmc_active_clock" SMIO
This is being developed in lnls-bpm/bpm-gw repo also, in commits from lnls-dig/bpm-gw@09f35bd8f7ec0477f80464cddfd6b8e3035435c5 to lnls-dig/bpm-gw@3c537b769f09fe8893bb78f2d646091ed8c2e227
Issue by lerwys Tuesday Apr 05, 2016 at 21:27 GMT Originally opened as https://github.com/lnls-dig/bpm-sw/issues/115
Problem: FMC130 and FMC250 both have the same exactly exported functions for the Active Clock part (AD9510 and SI571), but the functions are reimplemented on both SMIOs. This makes it harder to maintain.
Also, client applications, such as the EPICS IOC, are forced to access the same functions with different service names, "FMC130M_4CH" and "FMC250M_4CH", instead of a generic name as "FMC_ACTIVE_CLOCK"
Solution: Split the active clock part into the "fmc_active_clock" SMIO