summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2023-06-12 14:59:08 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2023-06-13 09:13:04 +0200
commit2baa16f2740b4546b1ec16390ec118ecba6be09d (patch)
tree78ff5703fb6d24aa08d6a5d898ed11ebf85d4396 /arch/arm/mach-omap
parentcfcd097c843194a6b88b03948afca3c4c547eca6 (diff)
downloadbarebox-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/mach-omap')
-rw-r--r--arch/arm/mach-omap/am33xx_scrm.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/mach-omap/am33xx_scrm.c b/arch/arm/mach-omap/am33xx_scrm.c
index c2ae73d53e..431e72fdda 100644
--- a/arch/arm/mach-omap/am33xx_scrm.c
+++ b/arch/arm/mach-omap/am33xx_scrm.c
@@ -36,6 +36,7 @@ static __maybe_unused struct of_device_id am33xx_scrm_dt_ids[] = {
/* sentinel */
}
};
+MODULE_DEVICE_TABLE(of, am33xx_scrm_dt_ids);
static struct driver am33xx_scrm_driver = {
.name = "am33xx-scrm",