Loading .gitignore +3 −0 Original line number Diff line number Diff line Loading @@ -132,3 +132,6 @@ all.config # Kdevelop4 *.kdev4 # fetched Android config fragments kernel/configs/android-*.cfg Documentation/ABI/testing/sysfs-kernel-wakeup_reasons 0 → 100644 +16 −0 Original line number Diff line number Diff line What: /sys/kernel/wakeup_reasons/last_resume_reason Date: February 2014 Contact: Ruchi Kandoi <kandoiruchi@google.com> Description: The /sys/kernel/wakeup_reasons/last_resume_reason is used to report wakeup reasons after system exited suspend. What: /sys/kernel/wakeup_reasons/last_suspend_time Date: March 2015 Contact: jinqian <jinqian@google.com> Description: The /sys/kernel/wakeup_reasons/last_suspend_time is used to report time spent in last suspend cycle. It contains two numbers (in seconds) separated by space. First number is the time spent in suspend and resume processes. Second number is the time spent in sleep state. No newline at end of file Documentation/admin-guide/kernel-parameters.txt +3 −0 Original line number Diff line number Diff line Loading @@ -884,6 +884,9 @@ dis_ucode_ldr [X86] Disable the microcode loader. dm= [DM] Allows early creation of a device-mapper device. See Documentation/device-mapper/boot.txt. dma_debug=off If the kernel is compiled with DMA_API_DEBUG support, this option disables the debugging code at boot. Loading Documentation/device-mapper/boot.txt 0 → 100644 +42 −0 Original line number Diff line number Diff line Boot time creation of mapped devices =================================== It is possible to configure a device mapper device to act as the root device for your system in two ways. The first is to build an initial ramdisk which boots to a minimal userspace which configures the device, then pivot_root(8) in to it. For simple device mapper configurations, it is possible to boot directly using the following kernel command line: dm="<name> <uuid> <ro>,table line 1,...,table line n" name = the name to associate with the device after boot, udev, if used, will use that name to label the device node. uuid = may be 'none' or the UUID desired for the device. ro = may be "ro" or "rw". If "ro", the device and device table will be marked read-only. Each table line may be as normal when using the dmsetup tool except for two variations: 1. Any use of commas will be interpreted as a newline 2. Quotation marks cannot be escaped and cannot be used without terminating the dm= argument. Unless renamed by udev, the device node created will be dm-0 as the first minor number for the device-mapper is used during early creation. Example ======= - Booting to a linear array made up of user-mode linux block devices: dm="lroot none 0, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" \ root=/dev/dm-0 Will boot to a rw dm-linear target of 8192 sectors split across two block devices identified by their major:minor numbers. After boot, udev will rename this target to /dev/mapper/lroot (depending on the rules). No uuid was assigned. Documentation/devicetree/bindings/misc/memory-state-time.txt 0 → 100644 +8 −0 Original line number Diff line number Diff line Memory bandwidth and frequency state tracking Required properties: - compatible : should be: "memory-state-time" - freq-tbl: Should contain entries with each frequency in Hz. - bw-buckets: Should contain upper-bound limits for each bandwidth bucket in Mbps. Must match the framework power_profile.xml for the device. Loading
.gitignore +3 −0 Original line number Diff line number Diff line Loading @@ -132,3 +132,6 @@ all.config # Kdevelop4 *.kdev4 # fetched Android config fragments kernel/configs/android-*.cfg
Documentation/ABI/testing/sysfs-kernel-wakeup_reasons 0 → 100644 +16 −0 Original line number Diff line number Diff line What: /sys/kernel/wakeup_reasons/last_resume_reason Date: February 2014 Contact: Ruchi Kandoi <kandoiruchi@google.com> Description: The /sys/kernel/wakeup_reasons/last_resume_reason is used to report wakeup reasons after system exited suspend. What: /sys/kernel/wakeup_reasons/last_suspend_time Date: March 2015 Contact: jinqian <jinqian@google.com> Description: The /sys/kernel/wakeup_reasons/last_suspend_time is used to report time spent in last suspend cycle. It contains two numbers (in seconds) separated by space. First number is the time spent in suspend and resume processes. Second number is the time spent in sleep state. No newline at end of file
Documentation/admin-guide/kernel-parameters.txt +3 −0 Original line number Diff line number Diff line Loading @@ -884,6 +884,9 @@ dis_ucode_ldr [X86] Disable the microcode loader. dm= [DM] Allows early creation of a device-mapper device. See Documentation/device-mapper/boot.txt. dma_debug=off If the kernel is compiled with DMA_API_DEBUG support, this option disables the debugging code at boot. Loading
Documentation/device-mapper/boot.txt 0 → 100644 +42 −0 Original line number Diff line number Diff line Boot time creation of mapped devices =================================== It is possible to configure a device mapper device to act as the root device for your system in two ways. The first is to build an initial ramdisk which boots to a minimal userspace which configures the device, then pivot_root(8) in to it. For simple device mapper configurations, it is possible to boot directly using the following kernel command line: dm="<name> <uuid> <ro>,table line 1,...,table line n" name = the name to associate with the device after boot, udev, if used, will use that name to label the device node. uuid = may be 'none' or the UUID desired for the device. ro = may be "ro" or "rw". If "ro", the device and device table will be marked read-only. Each table line may be as normal when using the dmsetup tool except for two variations: 1. Any use of commas will be interpreted as a newline 2. Quotation marks cannot be escaped and cannot be used without terminating the dm= argument. Unless renamed by udev, the device node created will be dm-0 as the first minor number for the device-mapper is used during early creation. Example ======= - Booting to a linear array made up of user-mode linux block devices: dm="lroot none 0, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" \ root=/dev/dm-0 Will boot to a rw dm-linear target of 8192 sectors split across two block devices identified by their major:minor numbers. After boot, udev will rename this target to /dev/mapper/lroot (depending on the rules). No uuid was assigned.
Documentation/devicetree/bindings/misc/memory-state-time.txt 0 → 100644 +8 −0 Original line number Diff line number Diff line Memory bandwidth and frequency state tracking Required properties: - compatible : should be: "memory-state-time" - freq-tbl: Should contain entries with each frequency in Hz. - bw-buckets: Should contain upper-bound limits for each bandwidth bucket in Mbps. Must match the framework power_profile.xml for the device.
