[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <24f1687c-043a-a15e-0be4-8392e7b5c96b@metux.net>
Date: Fri, 7 Aug 2020 13:25:58 +0200
From: "Enrico Weigelt, metux IT consult" <info@...ux.net>
To: Sven Van Asbroeck <thesven73@...il.com>,
Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Frank Rowand <frowand.list@...il.com>
Cc: David Airlie <airlied@...ux.ie>, Daniel Vetter <daniel@...ll.ch>,
devicetree <devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Q] devicetree overlays
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@...ux.net -- +49-151-27565287
Powered by blists - more mailing lists