From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Andy Gross <andy.gross@linaro.org>,
Jens Wiklander <jens.wiklander@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH 1/3] firmware: of: populate /firmware/ node during init
Date: Fri, 11 Aug 2017 16:16:14 +0100 [thread overview]
Message-ID: <7a3b73d0-988c-1d2a-43cc-4d30b4eac0f1@arm.com> (raw)
In-Reply-To: <CABGGisx7d+SQ7Sbyyu2hoNeuCFHZt1erjMg3zd5mHsqUF-Zk-Q@mail.gmail.com>
On 11/08/17 15:15, Rob Herring wrote:
> +Bjorn
>
> On Fri, Aug 11, 2017 at 8:30 AM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>> Since "/firmware" does not have its own "compatible" property as it's
>> just collection of nodes representing firmware interface, it's sub-nodes
>> are not populated during system initialization.
>>
>> Currently different firmware drivers search the /firmware/ node and
>> populate the sub-node devices selectively. Instead we can populate
>> the /firmware/ node during init to avoid more drivers continuing to
>> populate the devices selectively.
>>
>> This patch adds initcall to achieve the same.
>>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>> Cc: Rob Herring <robh@kernel.org>
>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>> ---
>> drivers/firmware/Makefile | 1 +
>> drivers/firmware/of.c | 34 ++++++++++++++++++++++++++++++++++
>> 2 files changed, 35 insertions(+)
>> create mode 100644 drivers/firmware/of.c
>>
>> diff --git a/drivers/firmware/Makefile b/drivers/firmware/Makefile
>> index 91d3ff62c653..d9a6fce43613 100644
>> --- a/drivers/firmware/Makefile
>> +++ b/drivers/firmware/Makefile
>> @@ -17,6 +17,7 @@ obj-$(CONFIG_ISCSI_IBFT) += iscsi_ibft.o
>> obj-$(CONFIG_FIRMWARE_MEMMAP) += memmap.o
>> obj-$(CONFIG_RASPBERRYPI_FIRMWARE) += raspberrypi.o
>> obj-$(CONFIG_FW_CFG_SYSFS) += qemu_fw_cfg.o
>> +obj-$(CONFIG_OF) += of.o
>> obj-$(CONFIG_QCOM_SCM) += qcom_scm.o
>> obj-$(CONFIG_QCOM_SCM_64) += qcom_scm-64.o
>> obj-$(CONFIG_QCOM_SCM_32) += qcom_scm-32.o
>> diff --git a/drivers/firmware/of.c b/drivers/firmware/of.c
>> new file mode 100644
>> index 000000000000..149b9660fb44
>> --- /dev/null
>> +++ b/drivers/firmware/of.c
>> @@ -0,0 +1,34 @@
>> +/*
>> + * Populates the nodes under /firmware/ device tree node
>> + *
>> + * Copyright (C) 2017 ARM Ltd.
>> + *
>> + * This file is subject to the terms and conditions of the GNU General Public
>> + * License. See the file "COPYING" in the main directory of this archive
>> + * for more details.
>> + *
>> + * Released under the GPLv2 only.
>
> Why do you have both the above 2 paragraphs and an SPDX tag? I'd drop
> the above (unless your lawyers told you otherwise).
>
I thought so initially but then just copied from existing file
(drivers/base/arch_topology.c in this case)
>> + * SPDX-License-Identifier: GPL-2.0
>> + */
>> +
>> +#include <linux/init.h>
>> +#include <linux/of.h>
>> +#include <linux/of_platform.h>
>> +
>> +static int __init firmware_of_init(void)
>
> I'd prefer this is added to of_platform_default_populate_init() and
> handled like /reserved-memory.
>
Yes that was my other option, wanted to check in the cover letter but
forgot.
> But be aware that Bjorn is reworking this function[1].
>
OK, thanks for the pointers.
>> +{
>> + struct device_node *fw_np;
>> + int ret;
>> +
>> + fw_np = of_find_node_by_name(NULL, "firmware");
>
> This matches any node named firmware. I see a few instances like RPi
> that are not /firmware (though RPi we can move probably).
> of_find_node_by_path would be safer.
>
OK
>> +
>> + if (!fw_np)
>> + return 0;
>> +
>> + ret = of_platform_populate(fw_np, NULL, NULL, NULL);
>> +
>> + of_node_put(fw_np);
>> +
>> + return ret;
>> +}
>> +arch_initcall_sync(firmware_of_init);
>
> You perhaps missed a few instances. "amlogic,meson-gxbb-sm" looks like
> it could be converted to a driver.
Indeed, was looking for the term "firmware" only :(, will add.
"tlm,trusted-foundations" appears
> to be needed early for bringing up cores, so it probably can't change.
That was my intially understand too when I looked at the way probe was
handled, but then I see it's module_init, so I went ahead with this change.
> They don't have to be converted as part of this series though.
>
OK
--
Regards,
Sudeep
next prev parent reply other threads:[~2017-08-11 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 13:30 [PATCH 0/3] " Sudeep Holla
2017-08-11 13:30 ` [PATCH 1/3] " Sudeep Holla
2017-08-11 14:15 ` Rob Herring
2017-08-11 15:16 ` Sudeep Holla [this message]
2017-08-11 15:22 ` Sudeep Holla
2017-08-11 14:37 ` Arnd Bergmann
2017-08-11 15:05 ` Rob Herring
2017-08-11 15:54 ` Arnd Bergmann
2017-08-14 13:28 ` Sudeep Holla
2017-09-27 16:54 ` Sudeep Holla
2017-08-11 15:37 ` Sudeep Holla
2017-08-11 13:30 ` [PATCH 2/3] firmware: qcom_scm: drop redandant of_platform_populate Sudeep Holla
2017-08-11 13:30 ` [PATCH 3/3] drivers: tee: rework optee_driver_{init,exit} to use platform device Sudeep Holla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a3b73d0-988c-1d2a-43cc-4d30b4eac0f1@arm.com \
--to=sudeep.holla@arm.com \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®