archive mirror
 help / color / mirror / Atom feed
From: Lizhi Hou <>
To: <>, <>
Cc: Lizhi Hou <>, <>,
	<>, <>,
	<>, <>,
	<>, <>,
	<>, <>, <>
Subject: [PATCH V2 Create empty OF root 0/1] XRT Alveo driver infrastructure overview
Date: Tue, 15 Feb 2022 21:00:55 -0800	[thread overview]
Message-ID: <> (raw)


This patch is to create an empty device tree if there is not one. For the use
case that hardware like Xilinx Alveo PCIe accelerator uses flattened device
tree to describe apertures in its PCIe BARs, a base tree with nodes for the
device needs to be created if there is not one. Then the flattened device tree
overlay from the device can be applied to the base tree. Please refer the
previous discussions with device tree maintainer:

This patch is the first step creates empty OF root node if the arch does not
have device tree created. I will post a follow on patch series to add PCIe
interface for the creation of device tree node for a PCIe device. This will
enable a PCIe device driver to apply an overlay under a PCIe device tree node.
Please refer previous discussions with FPGA maintainer:

We would like to use this infrastructure to describe and bind platform drivers
for HW IPs in Alveo PCIe accelerator device.

Lizhi Hou (1):
  of: create empty of root

 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


             reply	other threads:[~2022-02-16  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  5:00 Lizhi Hou [this message]
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
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).