Re: [PATCH 02/12] Kernel documentation for the PTI feature.

[Randy Dunlap]

On 2/8/2011 11:34 AM, james_p_freyensee@xxxxxxxxxxxxxxx wrote:
> From: J Freyensee<james_p_freyensee@xxxxxxxxxxxxxxx>
>
> This provides Kernel documentation for the PTI
> feature for Linux mobile solutions.
>
> Signed-off-by: J Freyensee<james_p_freyensee@xxxxxxxxxxxxxxx>
> ---
>   Documentation/pti/pti_intel_mid.txt |   89 +++++++++++++++++++++++++++++++++++
>   1 files changed, 89 insertions(+), 0 deletions(-)
>   create mode 100644 Documentation/pti/pti_intel_mid.txt
>
> diff --git a/Documentation/pti/pti_intel_mid.txt b/Documentation/pti/pti_intel_mid.txt
> new file mode 100644
> index 0000000..b9c3f3a
> --- /dev/null
> +++ b/Documentation/pti/pti_intel_mid.txt
> @@ -0,0 +1,89 @@
> +The Intel MID PTI project is HW implemented in Intel Atom
> +system-on-a-chip designs based on the Parallel Trace
> +Interface for MIPI P1149.7 cJTAG standard.  The kernel solution
> +for this platform involves the following files:
> +
> +./include/linux/pti.h
> +./include/linux/n_tracesink.h
> +./drivers/.../n_tracerouter.c
> +./drivers/.../n_tracesink.c
> +./drivers/.../pti.c
> +
> +pti.c is the driver that enables various debugging features
> +popular on certain mobile manufacturers.  n_tracerouter.c
> +and n_tracesink.c allow extra system information to be
> +collected and routed to the pti driver, such as trace
> +debugging data from a modem.  Altough n_tracerouter

                                 Although

> +and n_tracesink are a part of the complete PTI solution,
> +these two line disciplines can work separate from

                                       separately

> +pti.c and route any data stream from one /dev/tty node
> +to another /dev/tty node via kernel-space.  This provides
> +a stable, reliable connection that will not break unless
> +the user-space application shuts down (plus avoids
> +kernel->user->kernel context switch overheads of routing
> +data).

~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/