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 <sjg@chromium.org>
This commit is contained in:
parent
bc438b6e9a
commit
d472d821f3
@ -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
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user