Merge branches 'rmobile/ag5' and 'rmobile/fsi-despair' into rmobile-latest

Uwe Kleine-König <ukl@pengutronix.de>

Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com>

Valdis Kletnieks <Valdis.Kletnieks@vt.edu>

Takashi YOSHII <takashi.yoshii.zj@renesas.com>

	</orgname>

	<address>

	   <email>hjk@linutronix.de</email>

	   <email>hjk@hansjkoch.de</email>

	</address>

    </affiliation>

</author>

<para>If you know of any translations for this document, or you are

interested in translating it, please email me

<email>hjk@linutronix.de</email>.

<email>hjk@hansjkoch.de</email>.

</para>

</sect1>

<title>Feedback</title>

	<para>Find something wrong with this document? (Or perhaps something

	right?) I would love to hear from you. Please email me at

	<email>hjk@linutronix.de</email>.</para>

	<email>hjk@hansjkoch.de</email>.</para>

</sect1>

</chapter>

   inclusion, it should be accepted by a relevant subsystem maintainer -

   though this acceptance is not a guarantee that the patch will make it

   all the way to the mainline.  The patch will show up in the maintainer's

   subsystem tree and into the staging trees (described below).  When the

   subsystem tree and into the -next trees (described below).  When the

   process works, this step leads to more extensive review of the patch and

   the discovery of any problems resulting from the integration of this

   patch with work being done by others.

normally the right way to go.

2.4: STAGING TREES

2.4: NEXT TREES

The chain of subsystem trees guides the flow of patches into the kernel,

but it also raises an interesting question: what if somebody wants to look

the interesting subsystem trees, but that would be a big and error-prone

job.

The answer comes in the form of staging trees, where subsystem trees are

The answer comes in the form of -next trees, where subsystem trees are

collected for testing and review.  The older of these trees, maintained by

Andrew Morton, is called "-mm" (for memory management, which is how it got

started).  The -mm tree integrates patches from a long list of subsystem

Use of the MMOTM tree is likely to be a frustrating experience, though;

there is a definite chance that it will not even compile.

The other staging tree, started more recently, is linux-next, maintained by

The other -next tree, started more recently, is linux-next, maintained by

Stephen Rothwell.  The linux-next tree is, by design, a snapshot of what

the mainline is expected to look like after the next merge window closes.

Linux-next trees are announced on the linux-kernel and linux-next mailing

See http://lwn.net/Articles/289013/ for more information on this topic, and

stay tuned; much is still in flux where linux-next is involved.

Besides the mmotm and linux-next trees, the kernel source tree now contains

the drivers/staging/ directory and many sub-directories for drivers or

filesystems that are on their way to being added to the kernel tree

proper, but they remain in drivers/staging/ while they still need more

work.

2.4.1: STAGING TREES

The kernel source tree now contains the drivers/staging/ directory, where

many sub-directories for drivers or filesystems that are on their way to

being added to the kernel tree live.  They remain in drivers/staging while

they still need more work; once complete, they can be moved into the

kernel proper.  This is a way to keep track of drivers that aren't

up to Linux kernel coding or quality standards, but people may want to use

them and track development.

Greg Kroah-Hartman currently (as of 2.6.36) maintains the staging tree.

Drivers that still need work are sent to him, with each driver having

its own subdirectory in drivers/staging/.  Along with the driver source

files, a TODO file should be present in the directory as well.  The TODO

file lists the pending work that the driver needs for acceptance into

the kernel proper, as well as a list of people that should be Cc'd for any

patches to the driver.  Staging drivers that don't currently build should

have their config entries depend upon CONFIG_BROKEN.  Once they can

be successfully built without outside patches, CONFIG_BROKEN can be removed.

2.5: TOOLS

	char *p = (char *) page;

	tmp = simple_strtoul(p, &p, 10);

	if (!p || (*p && (*p != '\n')))

	if ((*p != '\0') && (*p != '\n'))

		return -EINVAL;

	if (tmp > INT_MAX)

		is configured as an output, this value may be written;

		any nonzero value is treated as high.

		If the pin can be configured as interrupt-generating interrupt

		and if it has been configured to generate interrupts (see the

		description of "edge"), you can poll(2) on that file and

		poll(2) will return whenever the interrupt was triggered. If

		you use poll(2), set the events POLLPRI and POLLERR. If you

		use select(2), set the file descriptor in exceptfds. After

		poll(2) returns, either lseek(2) to the beginning of the sysfs

		file and read the new value or close the file and re-open it

		to read the value.

	"edge" ... reads as either "none", "rising", "falling", or

		"both". Write these strings to select the signal edge(s)

		that will make poll(2) on the "value" file return.