From: Andrei Ziureaev <andreiziureaev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
andrei.ziureaev-5wv7dgnIgG8@public.gmane.org
Subject: [RFC PATCH v3 0/4] dtc: Add a plugin interface
Date: Sun, 6 Sep 2020 14:12:16 +0100 [thread overview]
Message-ID: <20200906131220.6192-1-andrei.ziureaev@arm.com> (raw)
I added a simple live tree API. There's no longer a need to move any
definitions. The live tree struct is hidden from plugins, so it's not an ABI.
The API doesn't allow plugins to modify the live tree yet, but that will
probably change later.
I also removed the EXPORT_FUNCTION macro. Plugins now have to implement
certain prototypes, defined in dtc-plugin.h. This allows plugins to be
generated by tools.
===========
This is one possible implementation of a plugin interface for DTC.
A plugin interface would allow us to add checks in languages other than
C. Specifically, it would allow DTC and DT Schema (which is written in
Python) to be integrated.
It would also allow for better debugging of dts files. For example, DT
Schema would be able to print dts source line information, without us
having to add source line annotations to yaml files.
In the future, plugins will be allowed to modify the live tree and pass
it back for further processing, but the API doesn't support that yet.
There's a question of whether we should relicense some headers to
dual BSD to be able call Python code.
Any thoughts would be much appreciated.
Thanks,
Andrei.
Changes in v3:
- live tree API (dt.h and dt.c)
- additional functionality in dtc.h
- plugins have to implement prototypes
- improved documentation
Changes in v2:
- improved documentation
- plugins must register with the build system
- the "validate_fn_t" hook can return a status
- define "struct reserve_info" in "dtc-plugin.h"
- specify that minor versions are compatible
- check if plugin_dir is NULL, just in case
- better variable names in register_plugin_info
Andrei Ziureaev (4):
dtc: Add marker type functionality to dtc.h
dtc: Add a live tree API
dtc: Add plugin documentation and examples
dtc: Add a plugin interface
Documentation/manual.txt | 146 ++++++++++++++++++++++++++++
Makefile | 29 +++++-
Makefile.dtc | 1 +
dt.c | 158 +++++++++++++++++++++++++++++++
dt.h | 63 ++++++++++++
dtc-plugin.h | 76 +++++++++++++++
dtc.c | 142 ++++++++++++++++++++++++++-
dtc.h | 57 +++++++++++
plugins/example/Makefile.example | 27 ++++++
plugins/example/example.c | 33 +++++++
treesource.c | 8 +-
11 files changed, 734 insertions(+), 6 deletions(-)
create mode 100644 dt.c
create mode 100644 dt.h
create mode 100644 dtc-plugin.h
create mode 100644 plugins/example/Makefile.example
create mode 100644 plugins/example/example.c
--
2.17.1
next reply other threads:[~2020-09-06 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 13:12 Andrei Ziureaev [this message]
[not found] ` <20200906131220.6192-1-andrei.ziureaev-5wv7dgnIgG8@public.gmane.org>
2020-09-06 13:12 ` [RFC PATCH v3 1/4] dtc: Add marker type functionality to dtc.h Andrei Ziureaev
2020-09-06 13:12 ` [RFC PATCH v3 2/4] dtc: Add a live tree API Andrei Ziureaev
[not found] ` <20200906131220.6192-3-andrei.ziureaev-5wv7dgnIgG8@public.gmane.org>
2020-09-07 1:44 ` Simon Glass
[not found] ` <CAPnjgZ09ve8x2kjx5KHqXJ9QFprk2uZdaKpAbTtaKYhA506gUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-09-07 13:02 ` Andrei Ziureaev
2020-09-06 13:12 ` [RFC PATCH v3 3/4] dtc: Add plugin documentation and examples Andrei Ziureaev
2020-09-06 13:12 ` [RFC PATCH v3 4/4] dtc: Add a plugin interface Andrei Ziureaev
2020-09-11 7:06 ` [RFC PATCH v3 0/4] " David Gibson
[not found] ` <20200911070640.GI66834-l+x2Y8Cxqc4e6aEkudXLsA@public.gmane.org>
2020-09-13 12:25 ` Andrei Ziureaev
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=20200906131220.6192-1-andrei.ziureaev@arm.com \
--to=andreiziureaev-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=andrei.ziureaev-5wv7dgnIgG8@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).