From: Simon Glass Date: Fri, 11 Sep 2020 02:21:25 +0000 (-0600) Subject: Kconfig: Move BOUNCE_BUFFER under driver options X-Git-Url: http://git.dujemihanovic.xyz/?a=commitdiff_plain;h=d472d821f35a4b4e5a2d3302948a6f95d8cadfa5;p=u-boot.git Kconfig: Move BOUNCE_BUFFER under driver options This option does not belong at the top level. Move it under generic driver options. Signed-off-by: Simon Glass --- diff --git a/common/Kconfig b/common/Kconfig index 132d105160..a1a898babd 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 1ca5d66141..07d3a6a7a4 100644 --- a/drivers/core/Kconfig +++ b/drivers/core/Kconfig @@ -286,4 +286,15 @@ config INTEL_ACPIGEN information such as P states and T stages. Also included is a way to create a GNVS table and set it up. +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