diff options
| author | Ahmad Fatoum <a.fatoum@pengutronix.de> | 2023-06-12 14:59:08 +0200 |
|---|---|---|
| committer | Sascha Hauer <s.hauer@pengutronix.de> | 2023-06-13 09:13:04 +0200 |
| commit | 2baa16f2740b4546b1ec16390ec118ecba6be09d (patch) | |
| tree | 78ff5703fb6d24aa08d6a5d898ed11ebf85d4396 /arch/arm/boards/pine64-quartz64 | |
| parent | cfcd097c843194a6b88b03948afca3c4c547eca6 (diff) | |
| download | barebox-2baa16f2740b4546b1ec16390ec118ecba6be09d.tar.gz barebox-2baa16f2740b4546b1ec16390ec118ecba6be09d.tar.xz | |
treewide: add MODULE_DEVICE_TABLE markers
Syncing device trees with Linux upstream can lead to breakage, when
the device trees are switched to newer bindings, which are not yet
supported in barebox. To make it easier to spot such issues, we want to
start applying some heuristics to flag possibly problematic DT changes.
One step towards being able to do that is to know what nodes barebox
actually consumes. Most of the nodes have a compatible entry, which is
matched by an array of of_device_id, so let's have MODULE_DEVICE_TABLE
point at it for future extraction.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Link: https://lore.barebox.org/20230612125908.1087340-1-a.fatoum@pengutronix.de
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'arch/arm/boards/pine64-quartz64')
| -rw-r--r-- | arch/arm/boards/pine64-quartz64/board.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/boards/pine64-quartz64/board.c b/arch/arm/boards/pine64-quartz64/board.c index caf7ff9cd4..1573dd8674 100644 --- a/arch/arm/boards/pine64-quartz64/board.c +++ b/arch/arm/boards/pine64-quartz64/board.c @@ -31,6 +31,7 @@ static const struct of_device_id quartz64_of_match[] = { }, { /* sentinel */ }, }; +MODULE_DEVICE_TABLE(of, quartz64_of_match); static struct driver quartz64_board_driver = { .name = "board-quartz64", |