From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752738AbdI1Kok (ORCPT ); Thu, 28 Sep 2017 06:44:40 -0400 Received: from foss.arm.com ([217.140.101.70]:54930 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751946AbdI1Koj (ORCPT ); Thu, 28 Sep 2017 06:44:39 -0400 From: Sudeep Holla To: linux-arm-kernel@lists.infradead.org Cc: Sudeep Holla , linux-kernel@vger.kernel.org, Rob Herring Subject: [RESEND][PATCH 0/4] firmware: of: populate /firmware/ node during init Date: Thu, 28 Sep 2017 11:44:27 +0100 Message-Id: <1506595471-10418-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, There's a push to place all firmware related device node under /firmware/ node. However all the associated drivers are dealing with device creation in their own ways. For example, qcom_scm, optee and meson-sm drivers deal with the node in their own way. The SCMI drivers I am about to add also needs to do the same. This small series is to make it generic so that all the users of /firmware/ node need not repeat the same. There was concern that /firmware in DT is fit for /sys/firmware in sysfs. IMO anything exposed to userspace from such firmware interface must be in "/sys/firmware", but I don't see any issue with kernel handling them as platform device/driver internally. Sudeep Holla (4): of: platform: populate /firmware/ node from of_platform_default_populate_init() firmware: qcom_scm: drop redandant of_platform_populate drivers: tee: rework optee_driver_{init,exit} to use platform device firmware: meson-sm: rework meson_sm_init to use module_platform_driver_probe drivers/firmware/meson/meson_sm.c | 21 ++++++----- drivers/firmware/qcom_scm.c | 24 ------------- drivers/of/platform.c | 4 +++ drivers/tee/optee/core.c | 74 +++++++++++++-------------------------- 4 files changed, 41 insertions(+), 82 deletions(-) -- 2.7.4