From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Chunyan Zhang <zhang.chunyan@linaro.org>,
laurent.fert@intel.com, yann.fouassier@intel.com,
linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [QUEUED v20160212 02/19] intel_th: Depend on HAS_IOMEM
Date: Fri, 12 Feb 2016 19:00:18 +0200 [thread overview]
Message-ID: <1455296435-17362-3-git-send-email-alexander.shishkin@linux.intel.com> (raw)
In-Reply-To: <1455296435-17362-1-git-send-email-alexander.shishkin@linux.intel.com>
This driver requires io memory to operate, so don't even consider it
for NO_IOMEM architectures.
Reported-by: Richard Weinberger <richard@nod.at>
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
---
drivers/hwtracing/intel_th/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwtracing/intel_th/Kconfig b/drivers/hwtracing/intel_th/Kconfig
index 90b0844093..1b412f8a56 100644
--- a/drivers/hwtracing/intel_th/Kconfig
+++ b/drivers/hwtracing/intel_th/Kconfig
@@ -1,6 +1,6 @@
config INTEL_TH
tristate "Intel(R) Trace Hub controller"
- depends on HAS_DMA
+ depends on HAS_DMA && HAS_IOMEM
help
Intel(R) Trace Hub (TH) is a set of hardware blocks (subdevices) that
produce, switch and output trace data from multiple hardware and
--
2.7.0
next prev parent reply other threads:[~2016-02-12 17:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 17:00 [QUEUED v20160212 00/19] stm class/intel_th: Patches in my queue Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 01/19] stm class: Use a signed return type for stm_find_master_chan Alexander Shishkin
2016-02-12 17:00 ` Alexander Shishkin [this message]
2016-02-12 17:00 ` [QUEUED v20160212 03/19] intel_th: gth: Remove commented-out code Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 04/19] intel_th: Update scratchpad bits according to enabled output activity Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 05/19] intel_th: msu: Fix offset for wrapped block Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 06/19] intel_th: msu: Release resources on read error Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 07/19] intel_th: sth: Sanitize packet callback's return values Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 08/19] intel_th: Set root device's drvdata early Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 09/19] intel_th: Use real device index in the node names Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 10/19] stm class: Use driver's packet callback return value Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 11/19] stm class: Support devices with multiple instances Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 12/19] stm class: dummy_stm: Create multiple devices Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 13/19] stm class: Add heartbeat stm source device Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 14/19] stm class: Fix unlocking braino in the error path Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 15/19] stm class: Guard output assignment against concurrency Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 16/19] stm class: Fix unbalanced module/device refcounting Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 17/19] stm class: Fix a race in unlinking Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 18/19] stm class: Plug stm device's unlink callback Alexander Shishkin
2016-02-12 17:00 ` [QUEUED v20160212 19/19] stm class: dummy_stm: Add link callback for fault injection Alexander Shishkin
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=1455296435-17362-3-git-send-email-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=greg@kroah.com \
--cc=laurent.fert@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=yann.fouassier@intel.com \
--cc=zhang.chunyan@linaro.org \
/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
all inboxes | Powered by JetHome®