[PATCH 14/16] Kconfig: Move BOUNCE_BUFFER under driver options

[Simon Glass]

This option does not belong at the top level. Move it under generic
driver options.

Signed-off-by: Simon Glass <sjg at chromium.org>
---

 common/Kconfig       | 11 -----------
 drivers/core/Kconfig | 11 +++++++++++
 2 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/common/Kconfig b/common/Kconfig
index 132d1051607..a1a898babd8 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -532,17 +532,6 @@ endmenu
 
 endmenu		# Init options
 
-config BOUNCE_BUFFER
-	bool "Include bounce buffer API"
-	help
-	  Some peripherals support DMA from a subset of physically
-	  addressable memory only.  To support such peripherals, the
-	  bounce buffer API uses a temporary buffer: it copies data
-	  to/from DMA regions while managing cache operations.
-
-	  A second possible use of bounce buffers is their ability to
-	  provide aligned buffers for DMA operations.
-
 config BOARD_TYPES
 	bool "Call get_board_type() to get and display the board type"
 	help
diff --git a/drivers/core/Kconfig b/drivers/core/Kconfig
index 00d1d80dc38..818bf85b64a 100644
--- a/drivers/core/Kconfig
+++ b/drivers/core/Kconfig
@@ -277,4 +277,15 @@ config ACPIGEN
 	  things like generating device-specific tables and returning the ACPI
 	  name of a device.
 
+config BOUNCE_BUFFER
+	bool "Include bounce buffer API"
+	help
+	  Some peripherals support DMA from a subset of physically
+	  addressable memory only.  To support such peripherals, the
+	  bounce buffer API uses a temporary buffer: it copies data
+	  to/from DMA regions while managing cache operations.
+
+	  A second possible use of bounce buffers is their ability to
+	  provide aligned buffers for DMA operations.
+
 endmenu
-- 
2.28.0.618.gf4bc123cb7-goog