summaryrefslogtreecommitdiff
path: root/drivers/ram
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2015-08-30 16:55:16 -0600
committerSimon Glass <sjg@chromium.org>2015-09-02 21:28:23 -0600
commit3346c87625b8a736af5636a0bd1be89f781eb5f2 (patch)
tree7fcd658cc520499f136add1e46643152618e9bf6 /drivers/ram
parente3563f2ec768fb989149362ca0c6ca4a27513924 (diff)
dm: Improve handling of a missing uclass
When a uclass definition is missing, no drivers in that uclass can operate. This can happen if a board has a strange collection of options (e.g. the driver is enabled but the uclass is not). Unfortunately this is very confusing at present. Starting up driver model results in a -ENOENT error, which is pretty generic. Quite a big of digging is needed to get to the root cause. To help with this, change the error to a very strange one with no other users in U-Boot. Also add a debug message. Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/ram')
0 files changed, 0 insertions, 0 deletions