From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: Sven Van Asbroeck <thesven73@gmail.com>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Frank Rowand <frowand.list@gmail.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Q] devicetree overlays
Date: Fri, 7 Aug 2020 13:25:58 +0200 [thread overview]
Message-ID: <24f1687c-043a-a15e-0be4-8392e7b5c96b@metux.net> (raw)
In-Reply-To: <CAGngYiVa9v9jGPNu4W+KHUnvemKU-BVE89-XNLcWOmoZjAPMTg@mail.gmail.com>
On 16.04.20 16:46, Sven Van Asbroeck wrote:
Hello folks,
> My situation is this: I have hardware which consists of several modules.
> Knowledge about the type and location of these modules is located in an
> on-board eeprom.
I've got a somewhat similar use cases, but not necessarily on DT-native
platforms:
a) composite devices that are probed via PCI or DMI and just instantiate
a bunch of other (more generic) devices.
For example the APUv2/3/4 board driver: it eg. instanciates the
gpio-amd-fch driver first, and then binds specific gpio lines to
appropriate functions, eg. reset key (input), LEDs, ...
b) I2C devices behind an USB-based bus adapter.
In both cases it would be nice to have the actual device configuration
written as a DT snippet, which just needs to be loaded.
Let me know, if anybody has an idea how to do that.
--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:[~2020-08-07 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 14:46 [Q] devicetree overlays Sven Van Asbroeck
2020-04-27 20:26 ` Frank Rowand
2020-04-28 12:20 ` Sven Van Asbroeck
2020-08-07 11:25 ` Enrico Weigelt, metux IT consult [this message]
2020-08-07 14:17 ` Sven Van Asbroeck
2020-08-12 13:27 ` Enrico Weigelt, metux IT consult
2020-08-12 14:43 ` Sven Van Asbroeck
2020-08-12 15:13 ` Frank Rowand
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=24f1687c-043a-a15e-0be4-8392e7b5c96b@metux.net \
--to=info@metux.net \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=thesven73@gmail.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).