From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: Frank Rowand <frowand.list@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
"Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Hans de Goede <hdegoede@redhat.com>
Subject: Re: [RFC PATCH 11/12] platform/x86: skeleton for oftree based board device initialization
Date: Tue, 23 Feb 2021 21:41:02 +0100 [thread overview]
Message-ID: <98005671-f0f4-02df-dbbf-b449c75a5da3@metux.net> (raw)
In-Reply-To: <f370fa7b-a5b1-4151-7018-10d1b75fa8b2@gmail.com>
On 15.02.21 02:18, Frank Rowand wrote:
> The RCAR use of overlays that are built into the driver are a known
> pattern that is explicitly not to be repeated.
Well, that driver indeed looks quite complex - if belive unnecessarily.
But can't judge on these devices, don't have one of them.
In my case, I believe it's a simple and straightforward approach,
instead of writing a whole driver, that just consists of a bunch
of tables and some trivial setup calls. DT seems to be a perfect
choice for that, since it's a very short and precise language for
describing hw layout, w/o any piece of imperative code.
The only point where I'm still not satisfied with: module auto-loading
requires the match data in the kernel module. But i'd like to have
everything in one source file and not having to write individual
modules for invididual boards anymore. Finally, there should be one
dts per board and really minimal effort adding another dts.
(hmm, maybe I should try generating glue code from dt ?)
BTW: I've already rewritten much of it, using overlay instead of an
completely own detached tree (so, some of the prev patches will fall
off the queue).
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2021-02-23 20:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 22:21 RFC: oftree based setup of composite board devices Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 01/12] of: base: improve error message in of_phandle_iterator_next() Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 02/12] of: base: introduce of_find_node_by_phandle_from() Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 03/12] of: base: record root node in interator and use it for phandle lookup Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 04/12] of: base: introduce of_match_string() Enrico Weigelt, metux IT consult
2021-02-08 23:52 ` Rob Herring
2021-02-08 22:21 ` [RFC PATCH 05/12] of: kobj: __of_attach_node_sysfs(): add optional basename parameter Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 06/12] of: kobj: introduce of_attach_tree_sysfs() Enrico Weigelt, metux IT consult
2021-02-08 22:21 ` [RFC PATCH 07/12] gpio: amd-fch: add oftree probing support Enrico Weigelt, metux IT consult
2021-02-11 9:57 ` Bartosz Golaszewski
2021-03-01 14:51 ` Linus Walleij
2021-03-11 10:17 ` Enrico Weigelt, metux IT consult
2021-03-11 10:42 ` Andy Shevchenko
2021-03-18 8:00 ` Enrico Weigelt, metux IT consult
2021-03-25 9:09 ` Linus Walleij
2021-02-08 22:21 ` [RFC PATCH 08/12] drivers: base: introduce bus_remove_device_by_name() Enrico Weigelt, metux IT consult
2021-02-08 22:22 ` [RFC PATCH 09/12] drivers: base: reintroduce find_bus() Enrico Weigelt, metux IT consult
2021-02-13 10:20 ` Greg KH
2021-02-23 20:13 ` Enrico Weigelt, metux IT consult
2021-02-24 8:00 ` Greg KH
2021-02-24 15:30 ` Enrico Weigelt, metux IT consult
2021-02-24 16:28 ` Greg KH
2021-02-08 22:22 ` [RFC PATCH 10/12] export bus_get() / bus_put() Enrico Weigelt, metux IT consult
2021-02-08 22:22 ` [RFC PATCH 11/12] platform/x86: skeleton for oftree based board device initialization Enrico Weigelt, metux IT consult
2021-02-10 10:32 ` Andy Shevchenko
2021-02-12 9:58 ` Linus Walleij
2021-02-12 11:54 ` Enrico Weigelt, metux IT consult
2021-02-15 1:18 ` Frank Rowand
2021-02-23 20:41 ` Enrico Weigelt, metux IT consult [this message]
2021-03-02 13:33 ` Linus Walleij
2021-02-08 22:22 ` [RFC PATCH 12/12] platform/x86/of: add support for PC Engines APU v2/3/4 boards Enrico Weigelt, metux IT consult
2021-02-09 0:06 ` Rob Herring
2021-02-11 13:15 ` Enrico Weigelt, metux IT consult
2021-03-01 14:55 ` Linus Walleij
2021-02-08 23:48 ` RFC: oftree based setup of composite board devices Rob Herring
2021-02-10 22:13 ` Enrico Weigelt, metux IT consult
2021-02-15 1:12 ` Frank Rowand
2021-02-15 15:35 ` Andy Shevchenko
2021-02-24 13:00 ` Enrico Weigelt, metux IT consult
2021-02-24 23:14 ` Frank Rowand
2021-03-05 18:29 ` Rob Herring
2021-02-10 10:30 ` Andy Shevchenko
2021-02-11 11:08 ` Enrico Weigelt, metux IT consult
2021-02-11 11:41 ` Andy Shevchenko
2021-02-11 17:01 ` Enrico Weigelt, metux IT consult
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=98005671-f0f4-02df-dbbf-b449c75a5da3@metux.net \
--to=info@metux.net \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=rafael@kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).