summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-imx/pcm970-baseboard.c
diff options
context:
space:
mode:
authorJon Hunter <jon-hunter@ti.com>2011-11-09 17:34:49 +0530
committerKevin Hilman <khilman@ti.com>2011-12-14 16:05:24 -0800
commita9e210e0b7a344c0e44aa6bf6888176bbc635c42 (patch)
treee24466ff2fd9c2f10979d5fce32a870c451448ff /arch/arm/mach-imx/pcm970-baseboard.c
parentc86845db77ce220f77e6645b18800744684946ac (diff)
downloadop-kernel-dev-a9e210e0b7a344c0e44aa6bf6888176bbc635c42.zip
op-kernel-dev-a9e210e0b7a344c0e44aa6bf6888176bbc635c42.tar.gz
ARM: OMAP2+: UART: Make the RX_TIMEOUT for DMA configurable for each UART
When using DMA there are two timeouts defined. The first timeout, rx_timeout, is really a polling rate in which software polls the DMA status to see if the DMA has finished. This is necessary for the RX side because we do not know how much data we will receive. The secound timeout, RX_TIMEOUT, is a timeout after which the DMA will be stopped if no more data is received. To make this clearer, rename rx_timeout as rx_poll_rate and rename the function serial_omap_rx_timeout() to serial_omap_rxdma_poll(). The OMAP-Serial driver defines an RX_TIMEOUT of 3 seconds that is used to indicate when the DMA for UART can be stopped if no more data is received. The value is a global definition that is applied to all instances of the UART. Each UART may be used for a different purpose and so the timeout required may differ. Make this value configurable for each UART so that this value can be optimised for power savings. Signed-off-by: Jon Hunter <jon-hunter@ti.com> Signed-off-by: Govindraj.R <govindraj.raja@ti.com> Acked-by: Greg Kroah-Hartman <gregkh@suse.de> (for drivers/tty changes) Signed-off-by: Kevin Hilman <khilman@ti.com>
Diffstat (limited to 'arch/arm/mach-imx/pcm970-baseboard.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud