From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753449AbdHKNbk (ORCPT ); Fri, 11 Aug 2017 09:31:40 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:44556 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753285AbdHKNaV (ORCPT ); Fri, 11 Aug 2017 09:30:21 -0400 From: Sudeep Holla To: linux-kernel@vger.kernel.org Cc: Sudeep Holla , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, Rob Herring , Arnd Bergmann , Andy Gross , Jens Wiklander Subject: [PATCH 0/3] firmware: of: populate /firmware/ node during init Date: Fri, 11 Aug 2017 14:30:34 +0100 Message-Id: <1502458237-1683-1-git-send-email-sudeep.holla@arm.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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