Hi Rob, Arnd, Recently Rob pointed to place SCMI device node under /firmware/ node and when I did that, I observed I had to populate the node first to get scmi node populated. Some research showed qcom_scm and optee drivers handle it in their own ways. This small series is to make it generic so that all the users of /firmware/ node need not repeat the same. Sudeep Holla (3): firmware: of: populate /firmware/ node during init firmware: qcom_scm: drop redandant of_platform_populate drivers: tee: rework optee_driver_{init,exit} to use platform device drivers/firmware/Makefile | 1 + drivers/firmware/of.c | 34 +++++++++++++++++++++ drivers/firmware/qcom_scm.c | 24 --------------- drivers/tee/optee/core.c | 74 +++++++++++++++------------------------------ 4 files changed, 60 insertions(+), 73 deletions(-) create mode 100644 drivers/firmware/of.c -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html