Searched hist:"8 cde3c2153e8f57be884c0e73f18bc4de150e870" (Results 1 – 3 of 3) sorted by relevance
| /linux/include/linux/firmware/meson/ |
| H A D | meson_sm.h | diff 8cde3c2153e8f57be884c0e73f18bc4de150e870 Wed Jul 31 10:23:39 CEST 2019 Carlo Caione <ccaione@baylibre.com> firmware: meson_sm: Rework driver as a proper platform driver
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@baylibre.com>
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
|
| /linux/drivers/nvmem/ |
| H A D | meson-efuse.c | diff 8cde3c2153e8f57be884c0e73f18bc4de150e870 Wed Jul 31 10:23:39 CEST 2019 Carlo Caione <ccaione@baylibre.com> firmware: meson_sm: Rework driver as a proper platform driver
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@baylibre.com>
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
|
| /linux/drivers/firmware/meson/ |
| H A D | meson_sm.c | diff 8cde3c2153e8f57be884c0e73f18bc4de150e870 Wed Jul 31 10:23:39 CEST 2019 Carlo Caione <ccaione@baylibre.com> firmware: meson_sm: Rework driver as a proper platform driver
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@baylibre.com>
Signed-off-by: Carlo Caione <ccaione@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
|