diff options
| author | Juergen Borleis <jbe@pengutronix.de> | 2017-08-17 11:32:32 +0200 |
|---|---|---|
| committer | Sascha Hauer <s.hauer@pengutronix.de> | 2017-09-06 14:02:56 +0200 |
| commit | 84ec1554e2a7b80202c01d6e04201bd5ea986cb7 (patch) | |
| tree | 4b6315fd6f859c63c3c264969070b294efa53e61 /crypto | |
| parent | 88ca962d6fc40d3654284df1f77c103b003e678f (diff) | |
| download | barebox-84ec1554e2a7b80202c01d6e04201bd5ea986cb7.tar.gz barebox-84ec1554e2a7b80202c01d6e04201bd5ea986cb7.tar.xz | |
state: use the given backend storage type name
Change 119f92b27e131a0cb506fe8d8bffe8010fb14a3d already tried to fix it, but
forgets the 'direct' usecase.
The 'backend-storage-type' node is optional. Its default depends on the
capability of the used backend memory, which means "circular" or NULL.
The latter defaults to 'direct' in the routines.
If it is NULL, the devicetree fixup routine skips exporting a
'backend-storage-type' node to the kernel's devicetree.
But currently if the 'backend-storage-type' node is explicitly given as
'direct', it will be skipped silently and set to NULL instead. In this
case the user of the 'barebox-state' tool then ends up with the warning:
"No backend-storage-type found, using default"
which is annoying, because it was given.
Storing the given value will still use a NULL if the
'backend-storage-type' node isn't defined, but stores everything else if
it is defined. Then the 'backend-storage-type' node is present in the
kernel's devicetree as well.
Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions