From: james_p_freyensee@linux.intel.com
To: gregkh@suse.de
Cc: linux-kernel@vger.kernel.org, suhail.ahmed@intel.com,
james_p_freyensee@linux.intel.com
Subject: [PATCH 04/12] PTI Kconfig change in misc.
Date: Tue, 8 Feb 2011 16:17:09 -0800 [thread overview]
Message-ID: <1297210637-5934-4-git-send-email-james_p_freyensee@linux.intel.com> (raw)
In-Reply-To: <1297210637-5934-3-git-send-email-james_p_freyensee@linux.intel.com>
From: J Freyensee <james_p_freyensee@linux.intel.com>
This adds the Intel PTI Kconfig option.
Signed-off-by: J Freyensee <james_p_freyensee@linux.intel.com>
---
drivers/misc/Kconfig | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 4d073f1..f8076f1 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -136,6 +136,18 @@ config PHANTOM
If you choose to build module, its name will be phantom. If unsure,
say N here.
+config INTEL_MID_PTI
+ tristate "Parallel Trace Interface for MIPI P1149.7 cJTAG standard"
+ help
+ The PTI (Parallel Trace Interface) driver directs
+ trace data routed from various parts in the system out
+ through an Intel Penwell PTI port and out of the mobile
+ device for analysis with a debugging tool (Lauterbach or Fido).
+
+ You should select this driver if the target kernel is meant for
+ an Intel Atom (non-netbook) mobile device containing a MIPI
+ P1149.7 standard implementation.
+
config SGI_IOC4
tristate "SGI IOC4 Base IO support"
depends on PCI
--
1.6.6.1
next prev parent reply other threads:[~2011-02-09 0:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 0:17 [PATCH 02/12] Kernel documentation for the PTI feature james_p_freyensee
2011-02-09 0:17 ` [PATCH 03/12] Intel PTI implementaiton of 1149 james_p_freyensee
2011-02-09 0:17 ` james_p_freyensee [this message]
2011-02-09 0:17 ` [PATCH 05/12] PTI misc Makefile addition james_p_freyensee
2011-02-09 0:17 ` [PATCH 06/12] PTI header file james_p_freyensee
2011-02-09 0:17 ` [PATCH 07/12] n_tracerouter and n_tracesink additions james_p_freyensee
2011-02-09 0:17 ` [PATCH 08/12] n_tracesink ldisc addition james_p_freyensee
2011-02-09 0:17 ` [PATCH 09/12] n_tracesink header file james_p_freyensee
2011-02-09 0:17 ` [PATCH 10/12] n_tracerouter ldisc driver james_p_freyensee
2011-02-09 0:17 ` [PATCH 11/12] n_tracerouter and n_tracesink Kconfig james_p_freyensee
2011-02-09 0:17 ` [PATCH 12/12] n_tracerouter and n_tracesink Makefile addition james_p_freyensee
2011-02-09 0:19 ` james_p_freyensee
[not found] ` <57934.10.23.16.85.1297210742.squirrel@linux.intel.com>
2011-02-09 0:34 ` PTI- PLEASE IGNORE SECOND DUPLICATE 12 PATCH SET james_p_freyensee
-- strict thread matches above, loose matches on Subject: below --
2011-02-08 19:34 Resend: Request for review and addition of PTI implementation into kernel james_p_freyensee
2011-02-08 19:34 ` [PATCH 01/12] export kernel call get_task_comm() james_p_freyensee
2011-02-08 19:34 ` [PATCH 02/12] Kernel documentation for the PTI feature james_p_freyensee
2011-02-08 19:34 ` [PATCH 03/12] Intel PTI implementaiton of 1149 james_p_freyensee
2011-02-08 19:34 ` [PATCH 04/12] PTI Kconfig change in misc james_p_freyensee
2011-02-17 19:20 ` Greg KH
2011-02-17 19:35 ` J Freyensee
2011-02-17 19:45 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1297210637-5934-4-git-send-email-james_p_freyensee@linux.intel.com \
--to=james_p_freyensee@linux.intel.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=suhail.ahmed@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).