summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2018-11-27 23:00:18 +0100
committerPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>2018-12-10 10:04:44 +0100
commitebb73de1687cfd6449f492b54cc2f32b4b0ce9c5 (patch)
tree944b0df2343457620b370027c174a7541578351c /arch
parentf338cca1d2bce906b049722d2fdbf527a4963b61 (diff)
downloadu-boot-ebb73de1687cfd6449f492b54cc2f32b4b0ce9c5.tar.gz
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 'arch')
0 files changed, 0 insertions, 0 deletions