From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932597AbdJPWoL (ORCPT ); Mon, 16 Oct 2017 18:44:11 -0400 Received: from mail-pf0-f194.google.com ([209.85.192.194]:52348 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932321AbdJPWoK (ORCPT ); Mon, 16 Oct 2017 18:44:10 -0400 X-Google-Smtp-Source: AOwi7QD5kiZMujss9vkk3532ibaYXVZcb/JiE7l8x+YdHzgW4Dy4zLZAJgztSxf/001Z0rcjf7dyWQ== Subject: Re: [RESEND][PATCH 0/4] firmware: of: populate /firmware/ node during init To: Sudeep Holla , linux-arm-kernel@lists.infradead.org References: <1506595562-10592-1-git-send-email-sudeep.holla@arm.com> Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Rob Herring , Frank Rowand From: Frank Rowand Message-ID: <59E53637.8020502@gmail.com> Date: Mon, 16 Oct 2017 15:44:07 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <1506595562-10592-1-git-send-email-sudeep.holla@arm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org + me On 09/28/17 03:45, Sudeep Holla wrote: > 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 > > -- > To unsubscribe from this list: send the line "unsubscribe devicetree" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >