ebb73de168
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> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| bootcount-uclass.c | ||
| bootcount.c | ||
| bootcount_at91.c | ||
| bootcount_davinci.c | ||
| bootcount_env.c | ||
| bootcount_ext.c | ||
| bootcount_i2c.c | ||
| bootcount_ram.c | ||