Merge branch 'sched/urgent' into sched/core (4d117c5c) · Commits · e / devices / android_kernel_teracube_2e

Documentation/cpu-freq/user-guide.txt

+12 −0

Original line number	Diff line number	Diff line
		@@ -23,6 +23,7 @@ Contents:
		1.3 sparc64
		1.4 ppc
		1.5 SuperH
		1.6 Blackfin

		2. "Policy" / "Governor"?
		2.1 Policy
		@@ -97,6 +98,17 @@ The following SuperH processors are supported by cpufreq:
		SH-3
		SH-4

		1.6 Blackfin
		------------

		The following Blackfin processors are supported by cpufreq:

		BF522, BF523, BF524, BF525, BF526, BF527, Rev 0.1 or higher
		BF531, BF532, BF533, Rev 0.3 or higher
		BF534, BF536, BF537, Rev 0.2 or higher
		BF561, Rev 0.3 or higher
		BF542, BF544, BF547, BF548, BF549, Rev 0.1 or higher


		2. "Policy" / "Governor" ?
		==========================

+6 −6

Original line number	Diff line number	Diff line
		@@ -130,12 +130,12 @@ The 2.6 kernel build process always creates a gzipped cpio format initramfs
		archive and links it into the resulting kernel binary. By default, this
		archive is empty (consuming 134 bytes on x86).

		The config option CONFIG_INITRAMFS_SOURCE (for some reason buried under
		devices->block devices in menuconfig, and living in usr/Kconfig) can be used
		to specify a source for the initramfs archive, which will automatically be
		incorporated into the resulting binary. This option can point to an existing
		gzipped cpio archive, a directory containing files to be archived, or a text
		file specification such as the following example:
		The config option CONFIG_INITRAMFS_SOURCE (in General Setup in menuconfig,
		and living in usr/Kconfig) can be used to specify a source for the
		initramfs archive, which will automatically be incorporated into the
		resulting binary. This option can point to an existing gzipped cpio
		archive, a directory containing files to be archived, or a text file
		specification such as the following example:

		dir /dev 755 0 0
		nod /dev/console 644 0 0 c 5 1

+2 −1

Original line number	Diff line number	Diff line
		@@ -20,10 +20,11 @@ pressed or released a BUTTON_IRQ happens. The driver could look like:

		static struct input_dev *button_dev;

		static void button_interrupt(int irq, void dummy, struct pt_regs fp)
		static irqreturn_t button_interrupt(int irq, void *dummy)
		{
		input_report_key(button_dev, BTN_0, inb(BUTTON_PORT) & 1);
		input_sync(button_dev);
		return IRQ_HANDLED;
		}

		static int __init button_init(void)

+4 −1

Original line number	Diff line number	Diff line
		@@ -1072,10 +1072,13 @@ Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
		ref Reference board
		dell-m4-1 Dell desktops
		dell-m4-2 Dell desktops
		dell-m4-3 Dell desktops

		STAC92HD73*
		ref Reference board
		dell-m6 Dell desktops
		dell-m6-amic Dell desktops/laptops with analog mics
		dell-m6-dmic Dell desktops/laptops with digital mics
		dell-m6 Dell desktops/laptops with both type of mics

		STAC9872
		vaio Setup for VAIO FE550G/SZ110

+4 −2

Original line number	Diff line number	Diff line
		@@ -37,7 +37,7 @@ $ echo mmiotrace > /debug/tracing/current_tracer
		$ cat /debug/tracing/trace_pipe > mydump.txt &
		Start X or whatever.
		$ echo "X is up" > /debug/tracing/trace_marker
		$ echo none > /debug/tracing/current_tracer
		$ echo nop > /debug/tracing/current_tracer
		Check for lost events.


		@@ -66,7 +66,7 @@ which action. It is recommended to place descriptive markers about what you
		do.

		Shut down mmiotrace (requires root privileges):
		$ echo none > /debug/tracing/current_tracer
		$ echo nop > /debug/tracing/current_tracer
		The 'cat' process exits. If it does not, kill it by issuing 'fg' command and
		pressing ctrl+c.

		@@ -81,7 +81,9 @@ are:
		$ cat /debug/tracing/trace_entries
		gives you a number. Approximately double this number and write it back, for
		instance:
		$ echo 0 > /debug/tracing/tracing_enabled
		$ echo 128000 > /debug/tracing/trace_entries
		$ echo 1 > /debug/tracing/tracing_enabled
		Then start again from the top.

		If you are doing a trace for a driver project, e.g. Nouveau, you should also