diff options
author | Simon Glass <sjg@chromium.org> | 2020-12-19 10:40:13 -0700 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2021-01-05 12:24:41 -0700 |
commit | 7d14ee443ca674314e0fe5c3e25f48e52a8fd5ee (patch) | |
tree | 2cf54ccfc6126a99a71b53fb4feaf7c0b4efa985 /drivers/timer | |
parent | c23405f8176c8d32d36ad992eb203ec87c4f5507 (diff) | |
download | u-boot-7d14ee443ca674314e0fe5c3e25f48e52a8fd5ee.tar.gz |
dm: core: Use dev_has_ofnode() instead of dev_of_valid()
We have two functions which do the same thing. Standardise on
dev_has_ofnode() since there is no such thing as an 'invalid' ofnode in
normal operation: it is either null or missing.
Also move the functions into one place.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Diffstat (limited to 'drivers/timer')
-rw-r--r-- | drivers/timer/timer-uclass.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/timer/timer-uclass.c b/drivers/timer/timer-uclass.c index 8e63c17e9f..da1a72f025 100644 --- a/drivers/timer/timer-uclass.c +++ b/drivers/timer/timer-uclass.c @@ -54,7 +54,7 @@ static int timer_pre_probe(struct udevice *dev) ulong ret; /* It is possible that a timer device has a null ofnode */ - if (!dev_of_valid(dev)) + if (!dev_has_ofnode(dev)) return 0; err = clk_get_by_index(dev, 0, &timer_clk); |