Loading Documentation/ABI/testing/sysfs-devices-power +18 −0 Original line number Original line Diff line number Diff line Loading @@ -165,3 +165,21 @@ Description: Not all drivers support this attribute. If it isn't supported, Not all drivers support this attribute. If it isn't supported, attempts to read or write it will yield I/O errors. attempts to read or write it will yield I/O errors. What: /sys/devices/.../power/pm_qos_latency_us Date: March 2012 Contact: Rafael J. Wysocki <rjw@sisk.pl> Description: The /sys/devices/.../power/pm_qos_resume_latency_us attribute contains the PM QoS resume latency limit for the given device, which is the maximum allowed time it can take to resume the device, after it has been suspended at run time, from a resume request to the moment the device will be ready to process I/O, in microseconds. If it is equal to 0, however, this means that the PM QoS resume latency may be arbitrary. Not all drivers support this attribute. If it isn't supported, it is not present. This attribute has no effect on system-wide suspend/resume and hibernation. Documentation/IRQ-domain.txt 0 → 100644 +117 −0 Original line number Original line Diff line number Diff line irq_domain interrupt number mapping library The current design of the Linux kernel uses a single large number space where each separate IRQ source is assigned a different number. This is simple when there is only one interrupt controller, but in systems with multiple interrupt controllers the kernel must ensure that each one gets assigned non-overlapping allocations of Linux IRQ numbers. The irq_alloc_desc*() and irq_free_desc*() APIs provide allocation of irq numbers, but they don't provide any support for reverse mapping of the controller-local IRQ (hwirq) number into the Linux IRQ number space. The irq_domain library adds mapping between hwirq and IRQ numbers on top of the irq_alloc_desc*() API. An irq_domain to manage mapping is preferred over interrupt controller drivers open coding their own reverse mapping scheme. irq_domain also implements translation from Device Tree interrupt specifiers to hwirq numbers, and can be easily extended to support other IRQ topology data sources. === irq_domain usage === An interrupt controller driver creates and registers an irq_domain by calling one of the irq_domain_add_*() functions (each mapping method has a different allocator function, more on that later). The function will return a pointer to the irq_domain on success. The caller must provide the allocator function with an irq_domain_ops structure with the .map callback populated as a minimum. In most cases, the irq_domain will begin empty without any mappings between hwirq and IRQ numbers. Mappings are added to the irq_domain by calling irq_create_mapping() which accepts the irq_domain and a hwirq number as arguments. If a mapping for the hwirq doesn't already exist then it will allocate a new Linux irq_desc, associate it with the hwirq, and call the .map() callback so the driver can perform any required hardware setup. When an interrupt is received, irq_find_mapping() function should be used to find the Linux IRQ number from the hwirq number. If the driver has the Linux IRQ number or the irq_data pointer, and needs to know the associated hwirq number (such as in the irq_chip callbacks) then it can be directly obtained from irq_data->hwirq. === Types of irq_domain mappings === There are several mechanisms available for reverse mapping from hwirq to Linux irq, and each mechanism uses a different allocation function. Which reverse map type should be used depends on the use case. Each of the reverse map types are described below: ==== Linear ==== irq_domain_add_linear() The linear reverse map maintains a fixed size table indexed by the hwirq number. When a hwirq is mapped, an irq_desc is allocated for the hwirq, and the IRQ number is stored in the table. The Linear map is a good choice when the maximum number of hwirqs is fixed and a relatively small number (~ < 256). The advantages of this map are fixed time lookup for IRQ numbers, and irq_descs are only allocated for in-use IRQs. The disadvantage is that the table must be as large as the largest possible hwirq number. The majority of drivers should use the linear map. ==== Tree ==== irq_domain_add_tree() The irq_domain maintains a radix tree map from hwirq numbers to Linux IRQs. When an hwirq is mapped, an irq_desc is allocated and the hwirq is used as the lookup key for the radix tree. The tree map is a good choice if the hwirq number can be very large since it doesn't need to allocate a table as large as the largest hwirq number. The disadvantage is that hwirq to IRQ number lookup is dependent on how many entries are in the table. Very few drivers should need this mapping. At the moment, powerpc iseries is the only user. ==== No Map ===- irq_domain_add_nomap() The No Map mapping is to be used when the hwirq number is programmable in the hardware. In this case it is best to program the Linux IRQ number into the hardware itself so that no mapping is required. Calling irq_create_direct_mapping() will allocate a Linux IRQ number and call the .map() callback so that driver can program the Linux IRQ number into the hardware. Most drivers cannot use this mapping. ==== Legacy ==== irq_domain_add_legacy() irq_domain_add_legacy_isa() The Legacy mapping is a special case for drivers that already have a range of irq_descs allocated for the hwirqs. It is used when the driver cannot be immediately converted to use the linear mapping. For example, many embedded system board support files use a set of #defines for IRQ numbers that are passed to struct device registrations. In that case the Linux IRQ numbers cannot be dynamically assigned and the legacy mapping should be used. The legacy map assumes a contiguous range of IRQ numbers has already been allocated for the controller and that the IRQ number can be calculated by adding a fixed offset to the hwirq number, and visa-versa. The disadvantage is that it requires the interrupt controller to manage IRQ allocations and it requires an irq_desc to be allocated for every hwirq, even if it is unused. The legacy map should only be used if fixed IRQ mappings must be supported. For example, ISA controllers would use the legacy map for mapping Linux IRQs 0-15 so that existing ISA drivers get the correct IRQ numbers. Documentation/devicetree/bindings/arm/exynos/power_domain.txt 0 → 100644 +21 −0 Original line number Original line Diff line number Diff line * Samsung Exynos Power Domains Exynos processors include support for multiple power domains which are used to gate power to one or more peripherals on the processor. Required Properties: - compatiable: should be one of the following. * samsung,exynos4210-pd - for exynos4210 type power domain. - reg: physical base address of the controller and length of memory mapped region. Optional Properties: - samsung,exynos4210-pd-off: Specifies that the power domain is in turned-off state during boot and remains to be turned-off until explicitly turned-on. Example: lcd0: power-domain-lcd0 { compatible = "samsung,exynos4210-pd"; reg = <0x10023C00 0x10>; }; Documentation/devicetree/bindings/arm/omap/omap.txt +6 −0 Original line number Original line Diff line number Diff line Loading @@ -41,3 +41,9 @@ Boards: - OMAP4 PandaBoard : Low cost community board - OMAP4 PandaBoard : Low cost community board compatible = "ti,omap4-panda", "ti,omap4430" compatible = "ti,omap4-panda", "ti,omap4430" - OMAP3 EVM : Software Developement Board for OMAP35x, AM/DM37x compatible = "ti,omap3-evm", "ti,omap3" - AM335X EVM : Software Developement Board for AM335x compatible = "ti,am335x-evm", "ti,am33xx", "ti,omap3" Documentation/devicetree/bindings/regulator/twl-regulator.txt 0 → 100644 +68 −0 Original line number Original line Diff line number Diff line TWL family of regulators Required properties: For twl6030 regulators/LDOs - compatible: - "ti,twl6030-vaux1" for VAUX1 LDO - "ti,twl6030-vaux2" for VAUX2 LDO - "ti,twl6030-vaux3" for VAUX3 LDO - "ti,twl6030-vmmc" for VMMC LDO - "ti,twl6030-vpp" for VPP LDO - "ti,twl6030-vusim" for VUSIM LDO - "ti,twl6030-vana" for VANA LDO - "ti,twl6030-vcxio" for VCXIO LDO - "ti,twl6030-vdac" for VDAC LDO - "ti,twl6030-vusb" for VUSB LDO - "ti,twl6030-v1v8" for V1V8 LDO - "ti,twl6030-v2v1" for V2V1 LDO - "ti,twl6030-clk32kg" for CLK32KG RESOURCE - "ti,twl6030-vdd1" for VDD1 SMPS - "ti,twl6030-vdd2" for VDD2 SMPS - "ti,twl6030-vdd3" for VDD3 SMPS For twl6025 regulators/LDOs - compatible: - "ti,twl6025-ldo1" for LDO1 LDO - "ti,twl6025-ldo2" for LDO2 LDO - "ti,twl6025-ldo3" for LDO3 LDO - "ti,twl6025-ldo4" for LDO4 LDO - "ti,twl6025-ldo5" for LDO5 LDO - "ti,twl6025-ldo6" for LDO6 LDO - "ti,twl6025-ldo7" for LDO7 LDO - "ti,twl6025-ldoln" for LDOLN LDO - "ti,twl6025-ldousb" for LDOUSB LDO - "ti,twl6025-smps3" for SMPS3 SMPS - "ti,twl6025-smps4" for SMPS4 SMPS - "ti,twl6025-vio" for VIO SMPS For twl4030 regulators/LDOs - compatible: - "ti,twl4030-vaux1" for VAUX1 LDO - "ti,twl4030-vaux2" for VAUX2 LDO - "ti,twl5030-vaux2" for VAUX2 LDO - "ti,twl4030-vaux3" for VAUX3 LDO - "ti,twl4030-vaux4" for VAUX4 LDO - "ti,twl4030-vmmc1" for VMMC1 LDO - "ti,twl4030-vmmc2" for VMMC2 LDO - "ti,twl4030-vpll1" for VPLL1 LDO - "ti,twl4030-vpll2" for VPLL2 LDO - "ti,twl4030-vsim" for VSIM LDO - "ti,twl4030-vdac" for VDAC LDO - "ti,twl4030-vintana2" for VINTANA2 LDO - "ti,twl4030-vio" for VIO LDO - "ti,twl4030-vdd1" for VDD1 SMPS - "ti,twl4030-vdd2" for VDD2 SMPS - "ti,twl4030-vintana1" for VINTANA1 LDO - "ti,twl4030-vintdig" for VINTDIG LDO - "ti,twl4030-vusb1v5" for VUSB1V5 LDO - "ti,twl4030-vusb1v8" for VUSB1V8 LDO - "ti,twl4030-vusb3v1" for VUSB3V1 LDO Optional properties: - Any optional property defined in bindings/regulator/regulator.txt Example: xyz: regulator@0 { compatible = "ti,twl6030-vaux1"; regulator-min-microvolt = <1000000>; regulator-max-microvolt = <3000000>; }; Loading
Documentation/ABI/testing/sysfs-devices-power +18 −0 Original line number Original line Diff line number Diff line Loading @@ -165,3 +165,21 @@ Description: Not all drivers support this attribute. If it isn't supported, Not all drivers support this attribute. If it isn't supported, attempts to read or write it will yield I/O errors. attempts to read or write it will yield I/O errors. What: /sys/devices/.../power/pm_qos_latency_us Date: March 2012 Contact: Rafael J. Wysocki <rjw@sisk.pl> Description: The /sys/devices/.../power/pm_qos_resume_latency_us attribute contains the PM QoS resume latency limit for the given device, which is the maximum allowed time it can take to resume the device, after it has been suspended at run time, from a resume request to the moment the device will be ready to process I/O, in microseconds. If it is equal to 0, however, this means that the PM QoS resume latency may be arbitrary. Not all drivers support this attribute. If it isn't supported, it is not present. This attribute has no effect on system-wide suspend/resume and hibernation.
Documentation/IRQ-domain.txt 0 → 100644 +117 −0 Original line number Original line Diff line number Diff line irq_domain interrupt number mapping library The current design of the Linux kernel uses a single large number space where each separate IRQ source is assigned a different number. This is simple when there is only one interrupt controller, but in systems with multiple interrupt controllers the kernel must ensure that each one gets assigned non-overlapping allocations of Linux IRQ numbers. The irq_alloc_desc*() and irq_free_desc*() APIs provide allocation of irq numbers, but they don't provide any support for reverse mapping of the controller-local IRQ (hwirq) number into the Linux IRQ number space. The irq_domain library adds mapping between hwirq and IRQ numbers on top of the irq_alloc_desc*() API. An irq_domain to manage mapping is preferred over interrupt controller drivers open coding their own reverse mapping scheme. irq_domain also implements translation from Device Tree interrupt specifiers to hwirq numbers, and can be easily extended to support other IRQ topology data sources. === irq_domain usage === An interrupt controller driver creates and registers an irq_domain by calling one of the irq_domain_add_*() functions (each mapping method has a different allocator function, more on that later). The function will return a pointer to the irq_domain on success. The caller must provide the allocator function with an irq_domain_ops structure with the .map callback populated as a minimum. In most cases, the irq_domain will begin empty without any mappings between hwirq and IRQ numbers. Mappings are added to the irq_domain by calling irq_create_mapping() which accepts the irq_domain and a hwirq number as arguments. If a mapping for the hwirq doesn't already exist then it will allocate a new Linux irq_desc, associate it with the hwirq, and call the .map() callback so the driver can perform any required hardware setup. When an interrupt is received, irq_find_mapping() function should be used to find the Linux IRQ number from the hwirq number. If the driver has the Linux IRQ number or the irq_data pointer, and needs to know the associated hwirq number (such as in the irq_chip callbacks) then it can be directly obtained from irq_data->hwirq. === Types of irq_domain mappings === There are several mechanisms available for reverse mapping from hwirq to Linux irq, and each mechanism uses a different allocation function. Which reverse map type should be used depends on the use case. Each of the reverse map types are described below: ==== Linear ==== irq_domain_add_linear() The linear reverse map maintains a fixed size table indexed by the hwirq number. When a hwirq is mapped, an irq_desc is allocated for the hwirq, and the IRQ number is stored in the table. The Linear map is a good choice when the maximum number of hwirqs is fixed and a relatively small number (~ < 256). The advantages of this map are fixed time lookup for IRQ numbers, and irq_descs are only allocated for in-use IRQs. The disadvantage is that the table must be as large as the largest possible hwirq number. The majority of drivers should use the linear map. ==== Tree ==== irq_domain_add_tree() The irq_domain maintains a radix tree map from hwirq numbers to Linux IRQs. When an hwirq is mapped, an irq_desc is allocated and the hwirq is used as the lookup key for the radix tree. The tree map is a good choice if the hwirq number can be very large since it doesn't need to allocate a table as large as the largest hwirq number. The disadvantage is that hwirq to IRQ number lookup is dependent on how many entries are in the table. Very few drivers should need this mapping. At the moment, powerpc iseries is the only user. ==== No Map ===- irq_domain_add_nomap() The No Map mapping is to be used when the hwirq number is programmable in the hardware. In this case it is best to program the Linux IRQ number into the hardware itself so that no mapping is required. Calling irq_create_direct_mapping() will allocate a Linux IRQ number and call the .map() callback so that driver can program the Linux IRQ number into the hardware. Most drivers cannot use this mapping. ==== Legacy ==== irq_domain_add_legacy() irq_domain_add_legacy_isa() The Legacy mapping is a special case for drivers that already have a range of irq_descs allocated for the hwirqs. It is used when the driver cannot be immediately converted to use the linear mapping. For example, many embedded system board support files use a set of #defines for IRQ numbers that are passed to struct device registrations. In that case the Linux IRQ numbers cannot be dynamically assigned and the legacy mapping should be used. The legacy map assumes a contiguous range of IRQ numbers has already been allocated for the controller and that the IRQ number can be calculated by adding a fixed offset to the hwirq number, and visa-versa. The disadvantage is that it requires the interrupt controller to manage IRQ allocations and it requires an irq_desc to be allocated for every hwirq, even if it is unused. The legacy map should only be used if fixed IRQ mappings must be supported. For example, ISA controllers would use the legacy map for mapping Linux IRQs 0-15 so that existing ISA drivers get the correct IRQ numbers.
Documentation/devicetree/bindings/arm/exynos/power_domain.txt 0 → 100644 +21 −0 Original line number Original line Diff line number Diff line * Samsung Exynos Power Domains Exynos processors include support for multiple power domains which are used to gate power to one or more peripherals on the processor. Required Properties: - compatiable: should be one of the following. * samsung,exynos4210-pd - for exynos4210 type power domain. - reg: physical base address of the controller and length of memory mapped region. Optional Properties: - samsung,exynos4210-pd-off: Specifies that the power domain is in turned-off state during boot and remains to be turned-off until explicitly turned-on. Example: lcd0: power-domain-lcd0 { compatible = "samsung,exynos4210-pd"; reg = <0x10023C00 0x10>; };
Documentation/devicetree/bindings/arm/omap/omap.txt +6 −0 Original line number Original line Diff line number Diff line Loading @@ -41,3 +41,9 @@ Boards: - OMAP4 PandaBoard : Low cost community board - OMAP4 PandaBoard : Low cost community board compatible = "ti,omap4-panda", "ti,omap4430" compatible = "ti,omap4-panda", "ti,omap4430" - OMAP3 EVM : Software Developement Board for OMAP35x, AM/DM37x compatible = "ti,omap3-evm", "ti,omap3" - AM335X EVM : Software Developement Board for AM335x compatible = "ti,am335x-evm", "ti,am33xx", "ti,omap3"
Documentation/devicetree/bindings/regulator/twl-regulator.txt 0 → 100644 +68 −0 Original line number Original line Diff line number Diff line TWL family of regulators Required properties: For twl6030 regulators/LDOs - compatible: - "ti,twl6030-vaux1" for VAUX1 LDO - "ti,twl6030-vaux2" for VAUX2 LDO - "ti,twl6030-vaux3" for VAUX3 LDO - "ti,twl6030-vmmc" for VMMC LDO - "ti,twl6030-vpp" for VPP LDO - "ti,twl6030-vusim" for VUSIM LDO - "ti,twl6030-vana" for VANA LDO - "ti,twl6030-vcxio" for VCXIO LDO - "ti,twl6030-vdac" for VDAC LDO - "ti,twl6030-vusb" for VUSB LDO - "ti,twl6030-v1v8" for V1V8 LDO - "ti,twl6030-v2v1" for V2V1 LDO - "ti,twl6030-clk32kg" for CLK32KG RESOURCE - "ti,twl6030-vdd1" for VDD1 SMPS - "ti,twl6030-vdd2" for VDD2 SMPS - "ti,twl6030-vdd3" for VDD3 SMPS For twl6025 regulators/LDOs - compatible: - "ti,twl6025-ldo1" for LDO1 LDO - "ti,twl6025-ldo2" for LDO2 LDO - "ti,twl6025-ldo3" for LDO3 LDO - "ti,twl6025-ldo4" for LDO4 LDO - "ti,twl6025-ldo5" for LDO5 LDO - "ti,twl6025-ldo6" for LDO6 LDO - "ti,twl6025-ldo7" for LDO7 LDO - "ti,twl6025-ldoln" for LDOLN LDO - "ti,twl6025-ldousb" for LDOUSB LDO - "ti,twl6025-smps3" for SMPS3 SMPS - "ti,twl6025-smps4" for SMPS4 SMPS - "ti,twl6025-vio" for VIO SMPS For twl4030 regulators/LDOs - compatible: - "ti,twl4030-vaux1" for VAUX1 LDO - "ti,twl4030-vaux2" for VAUX2 LDO - "ti,twl5030-vaux2" for VAUX2 LDO - "ti,twl4030-vaux3" for VAUX3 LDO - "ti,twl4030-vaux4" for VAUX4 LDO - "ti,twl4030-vmmc1" for VMMC1 LDO - "ti,twl4030-vmmc2" for VMMC2 LDO - "ti,twl4030-vpll1" for VPLL1 LDO - "ti,twl4030-vpll2" for VPLL2 LDO - "ti,twl4030-vsim" for VSIM LDO - "ti,twl4030-vdac" for VDAC LDO - "ti,twl4030-vintana2" for VINTANA2 LDO - "ti,twl4030-vio" for VIO LDO - "ti,twl4030-vdd1" for VDD1 SMPS - "ti,twl4030-vdd2" for VDD2 SMPS - "ti,twl4030-vintana1" for VINTANA1 LDO - "ti,twl4030-vintdig" for VINTDIG LDO - "ti,twl4030-vusb1v5" for VUSB1V5 LDO - "ti,twl4030-vusb1v8" for VUSB1V8 LDO - "ti,twl4030-vusb3v1" for VUSB3V1 LDO Optional properties: - Any optional property defined in bindings/regulator/regulator.txt Example: xyz: regulator@0 { compatible = "ti,twl6030-vaux1"; regulator-min-microvolt = <1000000>; regulator-max-microvolt = <3000000>; };
