Hi Caleb,
On Sun, 24 Nov 2024 at 12:17, Caleb Connolly caleb.connolly@linaro.org wrote:
SMEM is a highly Qualcomm specific interface, while having a dedicated
Qualcomm-specific
UCLASS for it offers a nice abstraction, for things like memory layout parsing we need to use it before the driver model is available.
As mentioned on irc, could you explain why that is, i.e. why not parse the memory layout after driver model is up, but still before relocation?
Therefore, it doesn't make sense to fit SMEM into the driver model. Instead let's adopt a model closer to Linux, and parse SMEM really early during boot (as soon as we have the FDT).
This reverts commit 7b384eccc785b596f68448b155cbda26df57fb23.
Signed-off-by: Caleb Connolly caleb.connolly@linaro.org
arch/arm/Kconfig | 1 - drivers/Kconfig | 2 -- drivers/Makefile | 1 - drivers/smem/Kconfig | 24 ------------- drivers/smem/Makefile | 7 ---- drivers/smem/smem-uclass.c | 46 ------------------------ include/dm/uclass-id.h | 1 - include/smem.h | 90 ---------------------------------------------- 8 files changed, 172 deletions(-)
Reviewed-by: Simon Glass sjg@chromium.org
Regards, Simon