diff options
| author | Philipp Tomsich <philipp.tomsich@theobroma-systems.com> | 2018-11-27 23:00:18 +0100 |
|---|---|---|
| committer | Philipp Tomsich <philipp.tomsich@theobroma-systems.com> | 2018-12-10 10:04:44 +0100 |
| commit | ebb73de1687cfd6449f492b54cc2f32b4b0ce9c5 (patch) | |
| tree | 944b0df2343457620b370027c174a7541578351c /drivers/bootcount/Makefile | |
| parent | f338cca1d2bce906b049722d2fdbf527a4963b61 (diff) | |
bootcount: add uclass for bootcount
The original bootcount methods do not provide an interface to DM and
rely on a static configuration for I2C devices (e.g. bus, chip-addr,
etc. are configured through defines statically). On a modern system
that exposes multiple devices in a DTS-configurable way, this is less
than optimal and a interface to DM-based devices will be desirable.
This adds a simple driver that is DM-aware and configurable via DTS.
If ambiguous (i.e. multiple bootcount-devices are present) the
/chosen/u-boot,bootcount-device property can be used to select one
bootcount device.
Initially, this provides support for the following DM devices:
* RTC devices
Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
Tested-by: Klaus Goger <klaus.goger@theobroma-systems.com>
Diffstat (limited to 'drivers/bootcount/Makefile')
| -rw-r--r-- | drivers/bootcount/Makefile | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/bootcount/Makefile b/drivers/bootcount/Makefile index 68bc006b75..81980b3cad 100644 --- a/drivers/bootcount/Makefile +++ b/drivers/bootcount/Makefile @@ -7,3 +7,5 @@ obj-$(CONFIG_BOOTCOUNT_RAM) += bootcount_ram.o obj-$(CONFIG_BOOTCOUNT_ENV) += bootcount_env.o obj-$(CONFIG_BOOTCOUNT_I2C) += bootcount_i2c.o obj-$(CONFIG_BOOTCOUNT_EXT) += bootcount_ext.o + +obj-$(CONFIG_DM_BOOTCOUNT) += bootcount-uclass.o |