Commit 86eedc66 authored by Markus Heidelberg's avatar Markus Heidelberg Committed by Rob Herring (Arm)
Browse files

docs: dt: fix grammar and spelling 



Signed-off-by: default avatarMarkus Heidelberg <m.heidelberg@cab.de>
Signed-off-by: default avatarRob Herring (Arm) <robh@kernel.org>
parent a036bb0e

Documentation/devicetree/of_unittest.rst

+2 −2
Original line number Diff line number Diff line
@@ -56,7 +56,7 @@ drivers/of/unittest.c. See the content of the folder:: 


for the Device Tree Source Include files (.dtsi) included in testcases.dts.



When the kernel is build with CONFIG_OF_UNITTEST enabled, then the following make

When the kernel is built with CONFIG_OF_UNITTEST enabled, then the following make

rule::



    $(obj)/%.dtb: $(src)/%.dts FORCE
@@ -133,7 +133,7 @@ via the following kernel symbols:: 
    __dtb_testcases_end   - address marking the end of test data blob



Secondly, it calls of_fdt_unflatten_tree() to unflatten the flattened

blob. And finally, if the machine's device tree (i.e live tree) is present,

blob. And finally, if the machine's device tree (i.e. live tree) is present,

then it attaches the unflattened test data tree to the live tree, else it

attaches itself as a live device tree.

Documentation/devicetree/overlay-notes.rst

+3 −3
Original line number Diff line number Diff line
@@ -14,11 +14,11 @@ How overlays work 
A Devicetree's overlay purpose is to modify the kernel's live tree, and

have the modification affecting the state of the kernel in a way that

is reflecting the changes.

Since the kernel mainly deals with devices, any new device node that result

Since the kernel mainly deals with devices, any new device node that results

in an active device should have it created while if the device node is either

disabled or removed all together, the affected device should be deregistered.



Lets take an example where we have a foo board with the following base tree::

Let's take an example where we have a foo board with the following base tree::



    ---- foo.dts ---------------------------------------------------------------

	/* FOO platform */

Documentation/devicetree/usage-model.rst

+3 −3
Original line number Diff line number Diff line
@@ -46,7 +46,7 @@ The DT was originally created by Open Firmware as part of the 
communication method for passing data from Open Firmware to a client

program (like to an operating system).  An operating system used the

Device Tree to discover the topology of the hardware at runtime, and

thereby support a majority of available hardware without hard coded

thereby supported a majority of available hardware without hard coded

information (assuming drivers were available for all devices).



Since Open Firmware is commonly used on PowerPC and SPARC platforms,
@@ -128,7 +128,7 @@ successor, the BeagleBoard xM board might look like, respectively:: 
	compatible = "ti,omap3-beagleboard-xm", "ti,omap3450", "ti,omap3";



Where "ti,omap3-beagleboard-xm" specifies the exact model, it also

claims that it compatible with the OMAP 3450 SoC, and the omap3 family

claims that it is compatible with the OMAP 3450 SoC, and the omap3 family

of SoCs in general.  You'll notice that the list is sorted from most

specific (exact board) to least specific (SoC family).