From patchwork Thu Sep 28 10:44:27 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Sudeep Holla X-Patchwork-Id: 114404 Delivered-To: patch@linaro.org Received: by 10.140.106.117 with SMTP id d108csp577568qgf; Thu, 28 Sep 2017 03:44:43 -0700 (PDT) X-Google-Smtp-Source: AOwi7QDUwUee3VFuOCVzXfXavi9Uw1XrSbV1dKcVSvMqa6MN7K1xr8QFCqsXtECimsrxf5nLmPRH X-Received: by 10.101.67.2 with SMTP id j2mr3854829pgq.182.1506595483006; Thu, 28 Sep 2017 03:44:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1506595483; cv=none; d=google.com; s=arc-20160816; b=MSxkTyw2WEk3+ue5/0Ym3QK3/NCcyHg+V8/iLw/+dHnhdj2u/zlUbI/Ye+4VDI4Ave eZiDZiH1O9rAB7D5X8ib4qeBJzeR7WTOnlHNNFCXXZigIbK8xDfCvGND9RiS7GGSw57/ Ag7gmEMnGI86lniV+NBdpG7OSmtgO+9bMqRLDgAE9jk/HurNVvi7ta5lkr4TENWPtF34 O7o0Zocz4r/CzpAovgIjuB1Sm92dRL5lUt4mXqSKWMvTmeXFCKLfSQjuplWi6Hasc1kC FGXeIGLCO/hD3M2Sxm8q5o6SPDFGSbp7sN2BEwPsW8W6yoV/Vo6sl1CHCPqxSFwlvcuy In7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=IZ/7wJl720hv+Ob/XHslw6kconqth/UPv7dTBQpuE1I=; b=tcorE6yxTBy7wpS1hGsL63CROHXEr/0A2FNn0rV6E7g/F6nr1nsuASKIahokKSX3zN jbPQngiukn4yqgvsVn9cZ/8C+7EcBj10zDIinhGflMhyNexJvbARFmW+ssdp9KiAatOW qeP3eGwx/qpSrbpzsyJX0P5qVCw/lf2zMHFJZ+mC5gjOqJt6G+HMplvz0BVRSHRb0Grv l6eXKN/E8Bp72HopLlZj9g53+Lwm47Pz21PTTYYIFgmzGQFRGYhNAG88u2Uxy7F9AMiI B+kq0+FC7sfbevxCQUNHb8ecCgxYkJXG3pQyZmEQkBjKklTCcAhAYW0PLu302TPiTSVn vT9g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d86si1137639pfb.370.2017.09.28.03.44.42; Thu, 28 Sep 2017 03:44:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752755AbdI1Kok (ORCPT + 26 others); 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 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 24CB41529; Thu, 28 Sep 2017 03:44:39 -0700 (PDT) Received: from e107155-lin.cambridge.arm.com (unknown [10.1.210.28]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 302DE3F53D; Thu, 28 Sep 2017 03:44:38 -0700 (PDT) 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 Precedence: bulk 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