path: root/Documentation/devicetree/changesets.txt
diff options
authorWolfram Sang <wsa+renesas@sang-engineering.com>2016-08-24 15:38:56 +0200
committerRob Herring <robh@kernel.org>2016-08-30 17:07:44 -0500
commit63b77d6d5a2dad95a9fe0c0459f10f632ae70248 (patch)
tree0292101ad1c8dcaca0c70fc9ec8f38f18ff5f2df /Documentation/devicetree/changesets.txt
parentLinux 4.8-rc3 (diff)
Documentation: devicetree: changesets do locking on their own meanwhile
Since commit 183223770ae862 ("drivers/of: Export OF changeset functions"), the mentioned functions do all necessary locking. Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Fixes: 183223770ae862 ("drivers/of: Export OF changeset functions") Signed-off-by: Rob Herring <robh@kernel.org>
Diffstat (limited to 'Documentation/devicetree/changesets.txt')
1 files changed, 5 insertions, 14 deletions
diff --git a/Documentation/devicetree/changesets.txt b/Documentation/devicetree/changesets.txt
index 935ba5acc34e..cb488eeb6353 100644
--- a/Documentation/devicetree/changesets.txt
+++ b/Documentation/devicetree/changesets.txt
@@ -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'
-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().