Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 63b77d6d authored by Wolfram Sang's avatar Wolfram Sang Committed by Rob Herring
Browse files

Documentation: devicetree: changesets do locking on their own meanwhile 



Since commit 18322377 ("drivers/of: Export OF changeset functions"),
the mentioned functions do all necessary locking.

Signed-off-by: default avatarWolfram Sang <wsa+renesas@sang-engineering.com>
Fixes: 18322377 ("drivers/of: Export OF changeset functions")
Signed-off-by: default avatarRob Herring <robh@kernel.org>
parent fa8410b3

Documentation/devicetree/changesets.txt

+5 −14
Original line number Diff line number Diff line
@@ -21,20 +21,11 @@ a set of changes. No changes to the active tree are made at this point. 
All the change operations are recorded in the of_changeset 'entries'

list.



3. mutex_lock(of_mutex) - starts a changeset; The global of_mutex

ensures there can only be one editor at a time.



4. of_changeset_apply() - Apply the changes to the tree. Either the

3. of_changeset_apply() - Apply the changes to the tree. Either the

entire changeset will get applied, or if there is an error the tree will

be restored to the previous state



5. mutex_unlock(of_mutex) - All operations complete, release the mutex

be restored to the previous state. The core ensures proper serialization

through locking. An unlocked version __of_changeset_apply is available,

if needed.



If a successfully applied changeset needs to be removed, it can be done

with the following sequence.



1. mutex_lock(of_mutex)



2. of_changeset_revert()



3. mutex_unlock(of_mutex)
 
with of_changeset_revert().