This probably should have been done a while back since it is a core system. Add a migration deadline of later this year, to catch the stragglers.
Signed-off-by: Simon Glass sjg@chromium.org ---
Changes in v4: - Refactored the warning code to make it easier to get this right - Add GPIO deprecation as well - Add patches to rename DM_RESET to RESET
Changes in v3: - s/'network'/I2C/ again
Changes in v2: - s/'network'/I2C/
Makefile | 1 + doc/driver-model/migration.rst | 8 ++++++++ 2 files changed, 9 insertions(+)
diff --git a/Makefile b/Makefile index 25e8f19a0cb..8e70da8d017 100644 --- a/Makefile +++ b/Makefile @@ -1097,6 +1097,7 @@ endif $(CONFIG_WATCHDOG)$(CONFIG_HW_WATCHDOG)) $(call deprecated,CONFIG_DM_ETH,Ethernet drivers,v2020.07,$(CONFIG_NET)) $(call deprecated,CONFIG_DM_I2C,I2C drivers,v2020.07,$(CONFIG_I2C)) + $(call deprecated,CONFIG_DM_GPIO,GPIO drivers,v2020.07,$(CONFIG_GPIO)) @# Check that this build does not use CONFIG options that we do not @# know about unless they are in Kconfig. All the existing CONFIG @# options are whitelisted, so new ones should not be added. diff --git a/doc/driver-model/migration.rst b/doc/driver-model/migration.rst index 8d0bb7635b5..20ff2c94b94 100644 --- a/doc/driver-model/migration.rst +++ b/doc/driver-model/migration.rst @@ -107,3 +107,11 @@ Deadline: 2021.10 The I2C subsystem has supported the driver model since early 2015. Maintainers should submit patches switching over to using CONFIG_DM_I2C and other base driver model options in time for inclusion in the 2021.10 release. + +CONFIG_DM_GPIO +-------------- +Deadline: 2021.10 + +The GPIO subsystem has supported the driver model since early 2014. +Maintainers should submit patches switching over to using CONFIG_DM_GPIO and +other base driver model options in time for inclusion in the 2021.10 release.