Merge branch 'perf/urgent' of...

		<title>Partition defines</title>

		<para>

			If you want to divide your device into partitions, then

			enable the configuration switch CONFIG_MTD_PARTITIONS and define

			a partitioning scheme suitable to your board.

			define a partitioning scheme suitable to your board.

		</para>

		<programlisting>

#define NUM_PARTITIONS 2

o	"dt" is the current value of the dyntick counter that is incremented

	when entering or leaving dynticks idle state, either by the

	scheduler or by irq.  The number after the "/" is the interrupt

	nesting depth when in dyntick-idle state, or one greater than

	the interrupt-nesting depth otherwise.

	This field is displayed only for CONFIG_NO_HZ kernels.

o	"dn" is the current value of the dyntick counter that is incremented

	when entering or leaving dynticks idle state via NMI.  If both

	the "dt" and "dn" values are even, then this CPU is in dynticks

	idle mode and may be ignored by RCU.  If either of these two

	counters is odd, then RCU must be alert to the possibility of

	an RCU read-side critical section running on this CPU.

	scheduler or by irq.  This number is even if the CPU is in

	dyntick idle mode and odd otherwise.  The number after the first

	"/" is the interrupt nesting depth when in dyntick-idle state,

	or one greater than the interrupt-nesting depth otherwise.

	The number after the second "/" is the NMI nesting depth.

	This field is displayed only for CONFIG_NO_HZ kernels.

      But each individual write to debugfs can implement a SINGLE

      method override. i.e. if we want to insert/override multiple

      ACPI methods, we need to redo step c) ~ g) for multiple times.

Note: Be aware that root can mis-use this driver to modify arbitrary

      memory and gain additional rights, if root's privileges got

      restricted (for example if root is not allowed to load additional

      modules after boot).

The boot loader must ultimately be able to provide a MACH_TYPE_xxx

value to the kernel. (see linux/arch/arm/tools/mach-types).

4. Setup the kernel tagged list

-------------------------------

4. Setup boot data

------------------

Existing boot loaders:		OPTIONAL, HIGHLY RECOMMENDED

New boot loaders:		MANDATORY

The boot loader must provide either a tagged list or a dtb image for

passing configuration data to the kernel.  The physical address of the

boot data is passed to the kernel in register r2.

4a. Setup the kernel tagged list

--------------------------------

The boot loader must create and initialise the kernel tagged list.

A valid tagged list starts with ATAG_CORE and ends with ATAG_NONE.

The ATAG_CORE tag may or may not be empty.  An empty ATAG_CORE tag

the kernel decompressor nor initrd 'bootp' program will overwrite

it.  The recommended placement is in the first 16KiB of RAM.

4b. Setup the device tree

-------------------------

The boot loader must load a device tree image (dtb) into system ram

at a 64bit aligned address and initialize it with the boot data.  The

dtb format is documented in Documentation/devicetree/booting-without-of.txt.

The kernel will look for the dtb magic value of 0xd00dfeed at the dtb

physical address to determine if a dtb has been passed instead of a

tagged list.

The boot loader must pass at a minimum the size and location of the

system memory, and the root filesystem location.  The dtb must be

placed in a region of memory where the kernel decompressor will not

overwrite it.  The recommended placement is in the first 16KiB of RAM

with the caveat that it may not be located at physical address 0 since

the kernel interprets a value of 0 in r2 to mean neither a tagged list

nor a dtb were passed.

5. Calling the kernel image

---------------------------

- CPU register settings

  r0 = 0,

  r1 = machine type number discovered in (3) above.

  r2 = physical address of tagged list in system RAM.

  r2 = physical address of tagged list in system RAM, or

       physical address of device tree block (dtb) in system RAM

- CPU mode

  All forms of interrupts must be disabled (IRQs and FIQs)

  - S3C24XX: See Documentation/arm/Samsung-S3C24XX/Overview.txt for full list

  - S3C64XX: S3C6400 and S3C6410

  - S5P6440

  - S5P6442

  - S5PC100

  - S5PC110 / S5PV210

  unifying all the SoCs into one kernel.

  s5p6440_defconfig - S5P6440 specific default configuration

  s5p6442_defconfig - S5P6442 specific default configuration

  s5pc100_defconfig - S5PC100 specific default configuration

  s5pc110_defconfig - S5PC110 specific default configuration

  s5pv210_defconfig - S5PV210 specific default configuration