linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Lizhi Hou <lizhi.hou@xilinx.com>,
	devicetree@vger.kernel.org, robh@kernel.org
Cc: linux-kernel@vger.kernel.org, yilun.xu@intel.com,
	maxz@xilinx.com, sonal.santan@xilinx.com, yliu@xilinx.com,
	michal.simek@xilinx.com, stefanos@xilinx.com, trix@redhat.com,
	mdf@kernel.org, dwmw2@infradead.org,
	Max Zhen <max.zhen@xilinx.com>
Subject: Re: [PATCH V2 Create empty OF root 1/1] of: create empty of root
Date: Mon, 16 May 2022 23:22:57 -0400	[thread overview]
Message-ID: <48b43291-b65a-0939-16ee-95b342e46377@gmail.com> (raw)
In-Reply-To: <20220216050056.311496-2-lizhi.hou@xilinx.com>

On 2/16/22 23:00, Lizhi Hou wrote:
> Xilinx Alveo PCIe accelerator cards use flattened device tree to describe
> describe apertures in its PCIe BARs. Each device tree node represents an
> aperture and each aperture is an hardware unit which requires a driver.
> The product detail:
>     https://www.xilinx.com/products/boards-and-kits/alveo.html
> 
> Thus a base device tree is required. Then the Alveo card driver can load
> its flattened device tree and overlay it to the base tree. However device
> tree does not always exist. To resolve this, add OF_EMPTY_ROOT config.
> When it is selected and there is not a device tree, create an empty device
> tree root node.
> 

Please run scripts/get_maintainer on your patches to see who to put in
the distribution list.

I recently stumbled across this patch series and the previous related
patch series (currently up to
"[PATCH V3 XRT Alveo Infrastructure 0/8] XRT Alveo driver infrastructure overview")
when I noticed it in an email archive.

A similar need of creating an of_root if otherwise empty is being discussed
in the thread "[PATCH 0/3] add dynamic PCI device of_node creation for overlay"
at https://lore.kernel.org/r/20220427094502.456111-1-clement.leger@bootlin.com

-Frank

> Signed-off-by: Sonal Santan <sonal.santan@xilinx.com>
> Signed-off-by: Max Zhen <max.zhen@xilinx.com>
> Signed-off-by: Lizhi Hou <lizhi.hou@xilinx.com>
> ---
>  drivers/of/Kconfig         |  5 ++++
>  drivers/of/Makefile        |  1 +
>  drivers/of/of_empty_root.c | 51 ++++++++++++++++++++++++++++++++++++++
>  3 files changed, 57 insertions(+)
>  create mode 100644 drivers/of/of_empty_root.c
> 
> diff --git a/drivers/of/Kconfig b/drivers/of/Kconfig
> index 80b5fd44ab1c..452d2316b47b 100644
> --- a/drivers/of/Kconfig
> +++ b/drivers/of/Kconfig
> @@ -94,4 +94,9 @@ config OF_DMA_DEFAULT_COHERENT
>  	# arches should select this if DMA is coherent by default for OF devices
>  	bool
>  
> +config OF_EMPTY_ROOT
> +	# driver which requires at least the empty base device tree to
> +	# overlay its own device nodes should select this.
> +	bool
> +
>  endif # OF
> diff --git a/drivers/of/Makefile b/drivers/of/Makefile
> index e0360a44306e..c65364f32935 100644
> --- a/drivers/of/Makefile
> +++ b/drivers/of/Makefile
> @@ -12,6 +12,7 @@ obj-$(CONFIG_OF_RESERVED_MEM) += of_reserved_mem.o
>  obj-$(CONFIG_OF_RESOLVE)  += resolver.o
>  obj-$(CONFIG_OF_OVERLAY) += overlay.o
>  obj-$(CONFIG_OF_NUMA) += of_numa.o
> +obj-$(CONFIG_OF_EMPTY_ROOT) += of_empty_root.o
>  
>  ifdef CONFIG_KEXEC_FILE
>  ifdef CONFIG_OF_FLATTREE
> diff --git a/drivers/of/of_empty_root.c b/drivers/of/of_empty_root.c
> new file mode 100644
> index 000000000000..5c429c7a27bd
> --- /dev/null
> +++ b/drivers/of/of_empty_root.c
> @@ -0,0 +1,51 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Copyright (C) 2022 Xilinx, Inc.
> + */
> +
> +#include <linux/of.h>
> +#include <linux/slab.h>
> +
> +#include "of_private.h"
> +
> +static int __init of_root_init(void)
> +{
> +	struct property *prop = NULL;
> +	struct device_node *node;
> +	__be32 *val = NULL;
> +
> +	if (of_root)
> +		return 0;
> +
> +	pr_info("Create empty OF root node\n");
> +	node = kzalloc(sizeof(*node), GFP_KERNEL);
> +	if (!node)
> +		return -ENOMEM;
> +	of_node_init(node);
> +	node->full_name = "/";
> +
> +	prop = kcalloc(2, sizeof(*prop), GFP_KERNEL);
> +	if (!prop)
> +		return -ENOMEM;
> +
> +	val = kzalloc(sizeof(*val), GFP_KERNEL);
> +	if (!val)
> +		return -ENOMEM;
> +	*val = cpu_to_be32(sizeof(void *) / sizeof(u32));
> +
> +	prop->name = "#address-cells";
> +	prop->value = val;
> +	prop->length = sizeof(u32);
> +	of_add_property(node, prop);
> +	prop++;
> +	prop->name = "#size-cells";
> +	prop->value = val;
> +	prop->length = sizeof(u32);
> +	of_add_property(node, prop);
> +	of_root = node;
> +	for_each_of_allnodes(node)
> +		__of_attach_node_sysfs(node);
> +
> +	return 0;
> +}
> +pure_initcall(of_root_init);


  reply	other threads:[~2022-05-17  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  5:00 [PATCH V2 Create empty OF root 0/1] XRT Alveo driver infrastructure overview Lizhi Hou
2022-02-16  5:00 ` [PATCH V2 Create empty OF root 1/1] of: create empty of root Lizhi Hou
2022-05-17  3:22   ` Frank Rowand [this message]
2022-05-18  5:02     ` Lizhi Hou

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=48b43291-b65a-0939-16ee-95b342e46377@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.hou@xilinx.com \
    --cc=max.zhen@xilinx.com \
    --cc=maxz@xilinx.com \
    --cc=mdf@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=robh@kernel.org \
    --cc=sonal.santan@xilinx.com \
    --cc=stefanos@xilinx.com \
    --cc=trix@redhat.com \
    --cc=yilun.xu@intel.com \
    --cc=yliu@xilinx.com \
    /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;
as well as URLs for NNTP newsgroup(s).