From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752936AbdI1Krb (ORCPT ); Thu, 28 Sep 2017 06:47:31 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:55052 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752729AbdI1Kra (ORCPT ); Thu, 28 Sep 2017 06:47:30 -0400 Cc: Sudeep Holla , linux-kernel@vger.kernel.org, Rob Herring Subject: Re: [RESEND][PATCH 0/4] firmware: of: populate /firmware/ node during init To: linux-arm-kernel@lists.infradead.org References: <1506595471-10418-1-git-send-email-sudeep.holla@arm.com> From: Sudeep Holla Organization: ARM Message-ID: <405d07ca-481a-724f-a579-0044ee359933@arm.com> Date: Thu, 28 Sep 2017 11:47:26 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1506595471-10418-1-git-send-email-sudeep.holla@arm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/09/17 11:44, 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. > Please ignore this, something went wrong and patches were not delivered, have reposted it separately. -- Regards, Sudeep