[PATCH] Explain what kind of bitmask is used in masks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Signed-off-by: Arkadiusz Drabczyk <arkadiusz@xxxxxxxxxxxx>
---
 source/devicetree-basics.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/devicetree-basics.rst b/source/devicetree-basics.rst
index 01b1958..bbb236a 100644
--- a/source/devicetree-basics.rst
+++ b/source/devicetree-basics.rst
@@ -1163,7 +1163,7 @@ Value type: ``<prop-encoded-array>`` encoded as a bit mask
 Description:
 
    An *interrupt-map-mask* property is specified for a nexus node in the
-   interrupt tree. This property specifies a mask that is applied to the
+   interrupt tree. This property specifies a mask that is ANDed with the
    incoming unit interrupt specifier being looked up in the table specified
    in the *interrupt-map* property.
 
@@ -1366,7 +1366,7 @@ Value type: ``<prop-encoded-array>`` encoded as a bit mask
 Description:
 
    A *<specifier>-map-mask* property may be specified for a nexus node.
-   This property specifies a mask that is applied to the child unit
+   This property specifies a mask that is ANDed with the child unit
    specifier being looked up in the table specified in the *<specifier>-map*
    property. If this property is not specified, the mask is assumed to be
    a mask with all bits set.
-- 
2.9.0




[Index of Archives]     [Device Tree]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux Audio Users]     [Photos]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]

  Powered by Linux