Loading Documentation/ABI/testing/sysfs-firmware-acpi +6 −2 Original line number Diff line number Diff line Loading @@ -69,9 +69,13 @@ Description: gpe1F: 0 invalid gpe_all: 1192 sci: 1194 sci_not: 0 sci - The total number of times the ACPI SCI has claimed an interrupt. sci - The number of times the ACPI SCI has been called and claimed an interrupt. sci_not - The number of times the ACPI SCI has been called and NOT claimed an interrupt. gpe_all - count of SCI caused by GPEs. Loading Documentation/filesystems/caching/cachefiles.txt +4 −4 Original line number Diff line number Diff line Loading @@ -407,7 +407,7 @@ A NOTE ON SECURITY ================== CacheFiles makes use of the split security in the task_struct. It allocates its own task_security structure, and redirects current->act_as to point to it its own task_security structure, and redirects current->cred to point to it when it acts on behalf of another process, in that process's context. The reason it does this is that it calls vfs_mkdir() and suchlike rather than Loading @@ -429,9 +429,9 @@ This means it may lose signals or ptrace events for example, and affects what the process looks like in /proc. So CacheFiles makes use of a logical split in the security between the objective security (task->sec) and the subjective security (task->act_as). The objective security holds the intrinsic security properties of a process and is never overridden. This is what appears in /proc, and is what is used when a objective security (task->real_cred) and the subjective security (task->cred). The objective security holds the intrinsic security properties of a process and is never overridden. This is what appears in /proc, and is what is used when a process is the target of an operation by some other process (SIGKILL for example). Loading Documentation/laptops/thinkpad-acpi.txt +2 −2 Original line number Diff line number Diff line ThinkPad ACPI Extras Driver Version 0.22 November 23rd, 2008 Version 0.23 April 10th, 2009 Borislav Deianov <borislav@users.sf.net> Henrique de Moraes Holschuh <hmh@hmh.eng.br> Loading Documentation/powerpc/booting-without-of.txt +12 −77 Original line number Diff line number Diff line Loading @@ -43,12 +43,11 @@ Table of Contents 2) Representing devices without a current OF specification a) PHY nodes b) Interrupt controllers c) CFI or JEDEC memory-mapped NOR flash d) 4xx/Axon EMAC ethernet nodes e) Xilinx IP cores f) USB EHCI controllers g) MDIO on GPIOs h) SPI busses c) 4xx/Axon EMAC ethernet nodes d) Xilinx IP cores e) USB EHCI controllers f) MDIO on GPIOs g) SPI busses VII - Marvell Discovery mv64[345]6x System Controller chips 1) The /system-controller node Loading Loading @@ -1287,71 +1286,7 @@ platforms are moved over to use the flattened-device-tree model. device_type = "open-pic"; }; c) CFI or JEDEC memory-mapped NOR flash Flash chips (Memory Technology Devices) are often used for solid state file systems on embedded devices. - compatible : should contain the specific model of flash chip(s) used, if known, followed by either "cfi-flash" or "jedec-flash" - reg : Address range of the flash chip - bank-width : Width (in bytes) of the flash bank. Equal to the device width times the number of interleaved chips. - device-width : (optional) Width of a single flash chip. If omitted, assumed to be equal to 'bank-width'. - #address-cells, #size-cells : Must be present if the flash has sub-nodes representing partitions (see below). In this case both #address-cells and #size-cells must be equal to 1. For JEDEC compatible devices, the following additional properties are defined: - vendor-id : Contains the flash chip's vendor id (1 byte). - device-id : Contains the flash chip's device id (1 byte). In addition to the information on the flash bank itself, the device tree may optionally contain additional information describing partitions of the flash address space. This can be used on platforms which have strong conventions about which portions of the flash are used for what purposes, but which don't use an on-flash partition table such as RedBoot. Each partition is represented as a sub-node of the flash device. Each node's name represents the name of the corresponding partition of the flash device. Flash partitions - reg : The partition's offset and size within the flash bank. - label : (optional) The label / name for this flash partition. If omitted, the label is taken from the node name (excluding the unit address). - read-only : (optional) This parameter, if present, is a hint to Linux that this flash partition should only be mounted read-only. This is usually used for flash partitions containing early-boot firmware images or data which should not be clobbered. Example: flash@ff000000 { compatible = "amd,am29lv128ml", "cfi-flash"; reg = <ff000000 01000000>; bank-width = <4>; device-width = <1>; #address-cells = <1>; #size-cells = <1>; fs@0 { label = "fs"; reg = <0 f80000>; }; firmware@f80000 { label ="firmware"; reg = <f80000 80000>; read-only; }; }; d) 4xx/Axon EMAC ethernet nodes c) 4xx/Axon EMAC ethernet nodes The EMAC ethernet controller in IBM and AMCC 4xx chips, and also the Axon bridge. To operate this needs to interact with a ths Loading Loading @@ -1499,7 +1434,7 @@ platforms are moved over to use the flattened-device-tree model. available. For Axon: 0x0000012a e) Xilinx IP cores d) Xilinx IP cores The Xilinx EDK toolchain ships with a set of IP cores (devices) for use in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range Loading Loading @@ -1793,7 +1728,7 @@ platforms are moved over to use the flattened-device-tree model. - reg-offset : A value of 3 is required - reg-shift : A value of 2 is required f) USB EHCI controllers e) USB EHCI controllers Required properties: - compatible : should be "usb-ehci". Loading @@ -1819,7 +1754,7 @@ platforms are moved over to use the flattened-device-tree model. big-endian; }; g) MDIO on GPIOs f) MDIO on GPIOs Currently defined compatibles: - virtual,gpio-mdio Loading @@ -1839,7 +1774,7 @@ platforms are moved over to use the flattened-device-tree model. &qe_pio_c 6>; }; h) SPI (Serial Peripheral Interface) busses g) SPI (Serial Peripheral Interface) busses SPI busses can be described with a node for the SPI master device and a set of child nodes for each SPI slave on the bus. For this Loading Documentation/powerpc/dts-bindings/mtd-physmap.txt 0 → 100644 +80 −0 Original line number Diff line number Diff line CFI or JEDEC memory-mapped NOR flash Flash chips (Memory Technology Devices) are often used for solid state file systems on embedded devices. - compatible : should contain the specific model of flash chip(s) used, if known, followed by either "cfi-flash" or "jedec-flash" - reg : Address range(s) of the flash chip(s) It's possible to (optionally) define multiple "reg" tuples so that non-identical NOR chips can be described in one flash node. - bank-width : Width (in bytes) of the flash bank. Equal to the device width times the number of interleaved chips. - device-width : (optional) Width of a single flash chip. If omitted, assumed to be equal to 'bank-width'. - #address-cells, #size-cells : Must be present if the flash has sub-nodes representing partitions (see below). In this case both #address-cells and #size-cells must be equal to 1. For JEDEC compatible devices, the following additional properties are defined: - vendor-id : Contains the flash chip's vendor id (1 byte). - device-id : Contains the flash chip's device id (1 byte). In addition to the information on the flash bank itself, the device tree may optionally contain additional information describing partitions of the flash address space. This can be used on platforms which have strong conventions about which portions of the flash are used for what purposes, but which don't use an on-flash partition table such as RedBoot. Each partition is represented as a sub-node of the flash device. Each node's name represents the name of the corresponding partition of the flash device. Flash partitions - reg : The partition's offset and size within the flash bank. - label : (optional) The label / name for this flash partition. If omitted, the label is taken from the node name (excluding the unit address). - read-only : (optional) This parameter, if present, is a hint to Linux that this flash partition should only be mounted read-only. This is usually used for flash partitions containing early-boot firmware images or data which should not be clobbered. Example: flash@ff000000 { compatible = "amd,am29lv128ml", "cfi-flash"; reg = <ff000000 01000000>; bank-width = <4>; device-width = <1>; #address-cells = <1>; #size-cells = <1>; fs@0 { label = "fs"; reg = <0 f80000>; }; firmware@f80000 { label ="firmware"; reg = <f80000 80000>; read-only; }; }; Here an example with multiple "reg" tuples: flash@f0000000,0 { #address-cells = <1>; #size-cells = <1>; compatible = "intel,PC48F4400P0VB", "cfi-flash"; reg = <0 0x00000000 0x02000000 0 0x02000000 0x02000000>; bank-width = <2>; partition@0 { label = "test-part1"; reg = <0 0x04000000>; }; }; Loading
Documentation/ABI/testing/sysfs-firmware-acpi +6 −2 Original line number Diff line number Diff line Loading @@ -69,9 +69,13 @@ Description: gpe1F: 0 invalid gpe_all: 1192 sci: 1194 sci_not: 0 sci - The total number of times the ACPI SCI has claimed an interrupt. sci - The number of times the ACPI SCI has been called and claimed an interrupt. sci_not - The number of times the ACPI SCI has been called and NOT claimed an interrupt. gpe_all - count of SCI caused by GPEs. Loading
Documentation/filesystems/caching/cachefiles.txt +4 −4 Original line number Diff line number Diff line Loading @@ -407,7 +407,7 @@ A NOTE ON SECURITY ================== CacheFiles makes use of the split security in the task_struct. It allocates its own task_security structure, and redirects current->act_as to point to it its own task_security structure, and redirects current->cred to point to it when it acts on behalf of another process, in that process's context. The reason it does this is that it calls vfs_mkdir() and suchlike rather than Loading @@ -429,9 +429,9 @@ This means it may lose signals or ptrace events for example, and affects what the process looks like in /proc. So CacheFiles makes use of a logical split in the security between the objective security (task->sec) and the subjective security (task->act_as). The objective security holds the intrinsic security properties of a process and is never overridden. This is what appears in /proc, and is what is used when a objective security (task->real_cred) and the subjective security (task->cred). The objective security holds the intrinsic security properties of a process and is never overridden. This is what appears in /proc, and is what is used when a process is the target of an operation by some other process (SIGKILL for example). Loading
Documentation/laptops/thinkpad-acpi.txt +2 −2 Original line number Diff line number Diff line ThinkPad ACPI Extras Driver Version 0.22 November 23rd, 2008 Version 0.23 April 10th, 2009 Borislav Deianov <borislav@users.sf.net> Henrique de Moraes Holschuh <hmh@hmh.eng.br> Loading
Documentation/powerpc/booting-without-of.txt +12 −77 Original line number Diff line number Diff line Loading @@ -43,12 +43,11 @@ Table of Contents 2) Representing devices without a current OF specification a) PHY nodes b) Interrupt controllers c) CFI or JEDEC memory-mapped NOR flash d) 4xx/Axon EMAC ethernet nodes e) Xilinx IP cores f) USB EHCI controllers g) MDIO on GPIOs h) SPI busses c) 4xx/Axon EMAC ethernet nodes d) Xilinx IP cores e) USB EHCI controllers f) MDIO on GPIOs g) SPI busses VII - Marvell Discovery mv64[345]6x System Controller chips 1) The /system-controller node Loading Loading @@ -1287,71 +1286,7 @@ platforms are moved over to use the flattened-device-tree model. device_type = "open-pic"; }; c) CFI or JEDEC memory-mapped NOR flash Flash chips (Memory Technology Devices) are often used for solid state file systems on embedded devices. - compatible : should contain the specific model of flash chip(s) used, if known, followed by either "cfi-flash" or "jedec-flash" - reg : Address range of the flash chip - bank-width : Width (in bytes) of the flash bank. Equal to the device width times the number of interleaved chips. - device-width : (optional) Width of a single flash chip. If omitted, assumed to be equal to 'bank-width'. - #address-cells, #size-cells : Must be present if the flash has sub-nodes representing partitions (see below). In this case both #address-cells and #size-cells must be equal to 1. For JEDEC compatible devices, the following additional properties are defined: - vendor-id : Contains the flash chip's vendor id (1 byte). - device-id : Contains the flash chip's device id (1 byte). In addition to the information on the flash bank itself, the device tree may optionally contain additional information describing partitions of the flash address space. This can be used on platforms which have strong conventions about which portions of the flash are used for what purposes, but which don't use an on-flash partition table such as RedBoot. Each partition is represented as a sub-node of the flash device. Each node's name represents the name of the corresponding partition of the flash device. Flash partitions - reg : The partition's offset and size within the flash bank. - label : (optional) The label / name for this flash partition. If omitted, the label is taken from the node name (excluding the unit address). - read-only : (optional) This parameter, if present, is a hint to Linux that this flash partition should only be mounted read-only. This is usually used for flash partitions containing early-boot firmware images or data which should not be clobbered. Example: flash@ff000000 { compatible = "amd,am29lv128ml", "cfi-flash"; reg = <ff000000 01000000>; bank-width = <4>; device-width = <1>; #address-cells = <1>; #size-cells = <1>; fs@0 { label = "fs"; reg = <0 f80000>; }; firmware@f80000 { label ="firmware"; reg = <f80000 80000>; read-only; }; }; d) 4xx/Axon EMAC ethernet nodes c) 4xx/Axon EMAC ethernet nodes The EMAC ethernet controller in IBM and AMCC 4xx chips, and also the Axon bridge. To operate this needs to interact with a ths Loading Loading @@ -1499,7 +1434,7 @@ platforms are moved over to use the flattened-device-tree model. available. For Axon: 0x0000012a e) Xilinx IP cores d) Xilinx IP cores The Xilinx EDK toolchain ships with a set of IP cores (devices) for use in Xilinx Spartan and Virtex FPGAs. The devices cover the whole range Loading Loading @@ -1793,7 +1728,7 @@ platforms are moved over to use the flattened-device-tree model. - reg-offset : A value of 3 is required - reg-shift : A value of 2 is required f) USB EHCI controllers e) USB EHCI controllers Required properties: - compatible : should be "usb-ehci". Loading @@ -1819,7 +1754,7 @@ platforms are moved over to use the flattened-device-tree model. big-endian; }; g) MDIO on GPIOs f) MDIO on GPIOs Currently defined compatibles: - virtual,gpio-mdio Loading @@ -1839,7 +1774,7 @@ platforms are moved over to use the flattened-device-tree model. &qe_pio_c 6>; }; h) SPI (Serial Peripheral Interface) busses g) SPI (Serial Peripheral Interface) busses SPI busses can be described with a node for the SPI master device and a set of child nodes for each SPI slave on the bus. For this Loading
Documentation/powerpc/dts-bindings/mtd-physmap.txt 0 → 100644 +80 −0 Original line number Diff line number Diff line CFI or JEDEC memory-mapped NOR flash Flash chips (Memory Technology Devices) are often used for solid state file systems on embedded devices. - compatible : should contain the specific model of flash chip(s) used, if known, followed by either "cfi-flash" or "jedec-flash" - reg : Address range(s) of the flash chip(s) It's possible to (optionally) define multiple "reg" tuples so that non-identical NOR chips can be described in one flash node. - bank-width : Width (in bytes) of the flash bank. Equal to the device width times the number of interleaved chips. - device-width : (optional) Width of a single flash chip. If omitted, assumed to be equal to 'bank-width'. - #address-cells, #size-cells : Must be present if the flash has sub-nodes representing partitions (see below). In this case both #address-cells and #size-cells must be equal to 1. For JEDEC compatible devices, the following additional properties are defined: - vendor-id : Contains the flash chip's vendor id (1 byte). - device-id : Contains the flash chip's device id (1 byte). In addition to the information on the flash bank itself, the device tree may optionally contain additional information describing partitions of the flash address space. This can be used on platforms which have strong conventions about which portions of the flash are used for what purposes, but which don't use an on-flash partition table such as RedBoot. Each partition is represented as a sub-node of the flash device. Each node's name represents the name of the corresponding partition of the flash device. Flash partitions - reg : The partition's offset and size within the flash bank. - label : (optional) The label / name for this flash partition. If omitted, the label is taken from the node name (excluding the unit address). - read-only : (optional) This parameter, if present, is a hint to Linux that this flash partition should only be mounted read-only. This is usually used for flash partitions containing early-boot firmware images or data which should not be clobbered. Example: flash@ff000000 { compatible = "amd,am29lv128ml", "cfi-flash"; reg = <ff000000 01000000>; bank-width = <4>; device-width = <1>; #address-cells = <1>; #size-cells = <1>; fs@0 { label = "fs"; reg = <0 f80000>; }; firmware@f80000 { label ="firmware"; reg = <f80000 80000>; read-only; }; }; Here an example with multiple "reg" tuples: flash@f0000000,0 { #address-cells = <1>; #size-cells = <1>; compatible = "intel,PC48F4400P0VB", "cfi-flash"; reg = <0 0x00000000 0x02000000 0 0x02000000 0x02000000>; bank-width = <2>; partition@0 { label = "test-part1"; reg = <0 0x04000000>; }; };
