[PATCH v3] timer: Add a migration message

Sean Anderson sean.anderson at seco.com
Sat Dec 18 00:23:21 CET 2021



On 12/17/21 6:12 PM, Simon Glass wrote:
> Some boards still use the old timer mechanism. Set a deadline for them to
> update to driver model. Point to some examples as well.
> 
> This needs a bit of a strange rule to avoid an error on some boards.
> 
> Signed-off-by: Simon Glass <sjg at chromium.org>
> ---
> 
> Changes in v3:
> - Push out the deadline
> 
>   Makefile                               |  4 ++++
>   doc/develop/driver-model/migration.rst | 12 ++++++++++++
>   2 files changed, 16 insertions(+)
> 
> diff --git a/Makefile b/Makefile
> index ab32efb4d11..7b24250103e 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1124,6 +1124,10 @@ endif
>   	$(call deprecated,CONFIG_DM_ETH,Ethernet drivers,v2020.07,$(CONFIG_NET))
>   	$(call deprecated,CONFIG_DM_I2C,I2C drivers,v2022.04,$(CONFIG_SYS_I2C_LEGACY))
>   	$(call deprecated,CONFIG_DM_KEYBOARD,Keyboard drivers,v2022.10,$(CONFIG_KEYBOARD))
> +	@# CONFIG_SYS_TIMER_RATE has brackets in it for some boards which
> +	@# confuses this rule. Use if() to send just a single character which
> +	@# is enable to tell 'deprecated' that one of these symbols exists
> +	$(call deprecated,CONFIG_TIMER,Timer drivers,v2023.01,$(if $(strip $(CONFIG_SYS_TIMER_RATE)$(CONFIG_SYS_TIMER_COUNTER)),x))
>   	@# 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/develop/driver-model/migration.rst b/doc/develop/driver-model/migration.rst
> index 3dbeea6537c..ed342bd4930 100644
> --- a/doc/develop/driver-model/migration.rst
> +++ b/doc/develop/driver-model/migration.rst
> @@ -106,3 +106,15 @@ Deadline: 2022.10
>   This is a legacy option which has been replaced by driver model.
>   Maintainers should submit patches switching over to using CONFIG_DM_KEYBOARD and
>   other base driver model options in time for inclusion in the 2022.10 release.
> +
> +CONFIG_SYS_TIMER_RATE and CONFIG_SYS_TIMER_COUNTER
> +--------------------------------------------------
> +Deadline: 2023.01
> +
> +These are legacy options which have been replaced by driver model.
> +Maintainers should submit patches switching over to using CONFIG_TIMER and
> +other base driver model options in time for inclusion in the 2022.10 release.
> +
> +There is only one method to implement, unless you want to support bootstage,
> +in which case you need an early timer alsol. For example drivers, see

nit: also

> +sandbox_timer.c and rockchip_timer.c
> 


More information about the U-Boot mailing list