On 31/07/2019 09:23, Carlo Caione wrote:
The secure monitor driver is currently a frankenstein driver which is registered as a platform driver but its functionality goes through a global struct accessed by the consumer drivers using exported helper functions. Try to tidy up the driver moving the firmware struct into the driver data and make the consumer drivers referencing the secure-monitor using a new property in the DT. Currently only the nvmem driver is using this API so we can fix it in the same commit. Reviewed-by: Jerome Brunet <jbrunet@xxxxxxxxxxxx> Signed-off-by: Carlo Caione <ccaione@xxxxxxxxxxxx> --- drivers/firmware/meson/meson_sm.c | 94 +++++++++++++++++-------- drivers/nvmem/meson-efuse.c | 24 ++++++-
Acked-by: Srinivas Kandagatla <srinivas.kandagatla@xxxxxxxxxx>
