NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide

From Texas Instruments Wiki
Jump to: navigation, search

TIBanner.png

Contents

Document License[edit]

This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/us/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.


Read This First[edit]

About This Manual[edit]

This document provides an overview and performance data for the device drivers which are part of the DaVinci Linux PSP package.

NOTE
For DA850/OMAP-L138/AM18xx EVM, the performance numbers have been recorded with cpuidle driver enabled and with cpufreq governor set to userspace.


If You Need Assistance[edit]

For further information or to report any problems, contact http://community.ti.com/ or http://support.ti.com/

Trademarks[edit]

OMAPTM and DaVinciTM are trademarks of Texas Instruments, Incorporated. All other trademarks are the properties of their respective owners.


Support Overview[edit]

Boot Modes Supported[edit]

The following table provides information on the boot modes supported in User Boot Loader (UBL). Green colored box in the table below means that the particular boot mode is supported on the device.

DaVinci Supported Boot Modes
Boot Mode DM644x DM6467 DM355 DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx
SPI EEPROM
SPI Flash
NAND Flash
NOR Flash
I2C EEPROM
MMC/SD


NOTE
These are supported boot modes in PSP software, the actual hardware may support many more boot modes than shown here. Please refer to hardware documentation for list of all supported boot modes.


U-Boot Support[edit]

U-Boot is the defacto bootloader for Linux kernel on ARM. The following features of U-Boot are supported in this release:

U-Boot supported feature table
Feature DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx
UART
Ethernet Download (TFTP)
USB DFU
MMC/SD
SPI Flash
NAND flash
NOR Flash
USB Mass Storage


Device Driver List[edit]

The following table list the various device drivers supported and the device they are supported on. On detailed information on specific features or limitations of a pariticular driver, refer to the chapter catering to that driver in this document.

Peripheral Driver Support
Peripheral Description Linux driver type DMA usage Devices supported on
Audio (McASP) Audio Record and Playback ALSA SoC EDMA3 DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
McBSP Serial Communication Interface Kernel API driver EDMA3 DA850/OMAP-L138/AM18xx
EMAC Ethernet Network driver Netdev

EMAC Internal DMA

DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
USB MSC Host USB Mass Storage Class Host Driver Block USB Internal DMA DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
USB HID Host USB Human Interface Device Host Driver Input driver USB Internal DMA DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
USB MUSB HCD MUSB Host controller driver USB HCD USB Internal DMA DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
USB OHCI HCD OHCI Host controller driver USB HCD USB Internal DMA DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
NAND Flash Flash storage system MTD Character and Block Not Supported
DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
NOR Flash Flash storage system MTD Character and Block Not Supported DA850/OMAP-L138/AM18xx
GLCD Graphical LCD driver Frame Buffer LCDC Internal DMA DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
CLCD Character LCD driver Parallel port based driver None DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
SPI Flash Flash storage system MTD Character and Block EDMA3 DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
MMC/SD Interface to MultiMedia Secure Digital cards Block EDMA3 DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
UART Serial Communication Interface Character Not Supported
DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
I2C Inter-IC Communication Character Not Supported
DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
RTC Real-time clock Character None DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
Watchdog Watchdog Timer Miscellaneous None DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
SPI (/dev/spi) Serial Peripheral Interface Character EDMA3 DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx
SATA Serial ATA Interface Block SATA Internal DMA DA850/OMAP-L138/AM18xx
Video Port Interface (VPIF) Video Display and Capture V4L2 (Video for Linux version 2) VPIF Internal DMA DA850/OMAP-L138/AM18xx
Power Management Linux drivers cpuidle, cpufreq and Suspend-to-RAM Misc None DA850/OMAP-L138/AM18xx
Touchscreen Drivers for TPS65070 and TSC2004 Input driver None DA830/OMAP-L137/AM17xx, DA850/OMAP-L138/AM18xx


ALSA SoC Audio Driver[edit]

Abstract

This chapter provides details on ALSA SoC audio driver along with CPU load numbers.

Introduction[edit]

DaVinci Audio driver complies to the Advanced Linux Sound Architecture (ALSA) System on Chip (SoC) framework (ASoC).

The ASoC framework splits an embedded audio system into three components:

  • Codec driver: The codec driver is generic and hardware independent code that configures the audio codec to provide audio capture and playback. It should contain no code that is specific to the target platform or machine.
  • Platform driver: The platform driver can be divided into audio DMA and SoC Digital Audio Interface (DAI) configuration and control. The platform driver only targets the SoC CPU and must have no board specific code.
  • Machine driver: The ASoC machine (or board) driver is the code that glues together the platform and codec drivers. It can contain codec and platform specific code. It registers the audio subsystem with the kernel as a platform device.

Following architecture diagram shows all the components and the interactions among them:

Audio.png

Driver Features[edit]

  1. The driver supports the following features:
  2. Supports AIC3106 audio codec in ALSA SoC framework.
  3. Multiple sample rate support (8 KHz, 44.1 KHz and 48 KHz commonly used) for both capture and playback.
  4. Supports audio in stereo mode.
  5. Supports simultaneous playback and record (full-duplex mode).
  6. Start, stop, pause and resume feature.
  7. Supports mixer interface for audio codecs.

Features Not Supported[edit]

  1. Does NOT support OSS based applications using OSS emulation layer.
  2. Driver will not work if built as module.

Constraints[edit]

  • By default, codec is configured in master mode and McASP is used as slave. Testing of the audio sub-system is done in this configuration only.
  • Configuration of playback and capture streams in different sampling rates is not supported.

Supported System Calls[edit]

Refer ALSA project - the C library reference [1] for API calls.

Supported IOCTLs[edit]

NA

Performance and Benchmarks[edit]

The performance numbers were captured using the following:

  • Word length in bits = 16
  • Number of channels per sample = 2


Audio Write Performance
Sampling Rate (in Hz) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz
8000 0 0
44100 1 1
48000 2 2 2


Audio Read Performance
Sampling Rate (in Hz) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz
8000 0 0 0 0
44100 1 1 1 1
48000 2 2 2 2


Ethernet Driver[edit]

Abstract

This chapter provides details on Ethernet driver along with throughput and CPU load numbers.

Introduction[edit]

The Ethernet driver supports the Linux netdev interface.

Ethernet.png

Driver Features[edit]

The driver supports the following features:

  1. 10/100 Mbps mode of operation.
  2. Auto negotiation.
  3. Support for multicast and broadcast frames.
  4. Promiscuous mode of operation.
  5. Full duplex and half duplex mode of operation.
  6. Linux NAPI support
  7. Support for MII and RMII interfaces to PHY

Features Not Supported[edit]

NA

Constraints[edit]

NA

Supported System Calls[edit]

Supports the socket() and related system calls in accordance with Linux architecture.

Performance and Benchmarks[edit]

Ethernet 100Mbps Mode Performance
TCP Window Size(in KBytes) Interval (in Seconds) Transfer Rate MII PHY (in Mbps) Transfer Rate RMII PHY (in Mbps)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
16 60 59.0 68.3 57.7 62.8 58.44 66.3 NA NA
32 60 66.7 78.6  66.1 72.9 65.7 76.7 NA NA
64 60 66.3 78.6 67.2 75.6 65.8 76.9 NA NA
128 60 66.6 78.5 67.4 75.1 65.9 76.1 NA NA


NOTES
RMII PHY support is available only on DA850/OMAPL138/AM18xx.
CPU load during the performance test is 100%

The performance numbers were captured using the iperf tool. Usage details are mentioned below:

  • Server side command switch : "-s"
  • Client side command : "-c <server ip> -w <window size> -d -t60". This starts bi-directional traffic to the server for a duration of 60 seconds.
  • Iperf tool is run on the DUT1 in server mode and on DUT2 in client mode. Version 2.0.4 is used on both sides.
  • Data captured here is for "iperf" in client mode.
  • Cross cable is used to measure performance.
  • Speed is set to 100Mbps


Graphical LCD (GLCD) Driver[edit]

Abstract

This chapter describes the GLCD driver architecture, driver features and performance numbers (throughput and CPU load).

Introduction[edit]

GLCD driver is based on Fbdev framework.

Note: On OMAP-L137, the EVM does not have Graphical LCD populated. The LCD panel available on DA830 EVM UI card has been used for testing.

GLCD Driver.jpg

Driver Features[edit]

  1. Supports QVGA display through Fbdev framework.
  2. Supports display of RGB565 images.
  3. Supports getting and setting the variable screen information.
  4. Supports retrieving the fixed screen information.

Features Not Supported[edit]

  1. WAITFORVSYNC ioctl not supported.
  2. Panning not supported.
  3. Brightness and color control ioctls not supported.

Constraints[edit]

  1. Driver doesn't support double buffering.

Supported System Calls[edit]

open(), close(), read(), mmap(), ioctl()

Performance Benchmarks[edit]


NAND Driver[edit]

Abstract

This chapter describes the NAND flash driver architecture, driver features and performance numbers (throughput and CPU load).

Introduction[edit]

The NAND driver is implemented as a character and block driver, compliant with the Linux MTD subsystem interface. It supports various NAND Flash chips (see file drivers/mtd/nand/nand_ids.h in Linux kernel sources) The NAND driver creates the device nodes for user space access (/dev/mtdblock0, /dev/mtdblock1, /dev/mtd0,/dev/mtd1 and so on.).

Note: On OMAP-L137, the EVM does not have NAND device populated. The NAND device available on DA830 EVM UI card has been used for testing.

This figure illustrates the stack diagram of NAND flash driver in Linux.

Nand Driver.png

Driver Features[edit]

The driver supports the following features:

  1. JFFS2 file system support
  2. Supports Read, Write and Erase
  3. Bad Block Management
  4. Polled mode of transfer
  5. Small Block (512 bytes), Big Block (2K & 4K bytes), SLC NAND

Features Not Supported[edit]

  1. flash_eraseall with -j option fails. Please use without -j option

Constraints[edit]

None

Supported System Calls[edit]

Supports the system call support proivided by Linux MTD interface viz. open(), close(), read(), write(), ioctl()

Performance Benchmarks[edit]

NAND Write performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 3.26 4.15  3.26 4.02  98.95 100.00  100.00 100.00 
256 100 3.32 4.07 3.08 3.81 98.50 100.00 100.00 100.00
512 100 3.14 3.86 2.93 3.61 99.29 100.00 100.00 100.00
1024 100 2.98 3.64 2.79 3.42 99.04 100.00 100.00 100.00
5120 100 2.79 3.46 2.66 3.24 99.08 100.00 100.00 100.00


NAND Read performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 8.54 11.05  8.36 10.32  95.42 100.00  100.00 100.00 
256 100 8.34 10.93 8.38 10.17 100.00 100.00 100.00 100.00
512 100 8.29 10.82 8.38 10.05 99.61 100.00 100.00 100.00
1024 100 8.37 10.91 8.35 10.31 99.61 100.00 100.00 100.00
5120 100 8.26 10.92 8.36 9.93 99.61 100.00 100.00 100.00


The performance numbers are captured using the following:

  1. NAND PART Number: Micron MT29F4G08AAC
  2. File System = JFFS2
  3. NAND partition was mounted with async option.


NOR flash Driver[edit]

Abstract

This chapter describes the NOR flash driver architecture, driver features and performance numbers (throughput and CPU load).

Introduction[edit]

The NOR flash driver is implemented as a character and block device driver, compliant with the Linux MTD subsystem architecture. It supports various CFI compliant NOR flash chips. The NOR flash driver creates the device nodes for user space access (/dev/mtdblock0, /dev/mtdblock1, /dev/mtd0,/dev/mtd1 and so on.).

Driver Features[edit]

The driver supports the following features:

  1. JFFS2 file system support
  2. Supports Read, Write and Erase
  3. Polled mode of transfer

Features Not Supported[edit]

None

Constraints[edit]

None

Supported System Calls[edit]

Supports the system call support proivided by Linux MTD interface viz. open(), close(), read(), write(), ioctl()

Performance Benchmarks[edit]

NOR Write performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 2.00 1.78 NA NA 100.00 100.00 NA NA
256 100 2.16 2.16 NA NA 100.00 100.00 NA NA
512 100 2.12 2.12 NA NA 100.00 100.00 NA NA
1024 100 2.06 2.05 NA NA 100.00 100.00 NA NA
5120 100 2.00 2.00 NA NA 100.00 100.00 NA NA


NOR Read performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 10.82 10.78 NA NA 100.00 100.00 NA NA
256 100 10.93 10.91 NA NA 100.00 100.00 NA NA
512 100 10.80 10.73 NA NA 100.00 100.00 NA NA
1024 100 10.99 10.98 NA NA 100.00 100.00 NA NA
5120 100 10.61 10.68 NA NA 100.00 100.00 NA NA


NOTE
NOR driver support is available only on DA850/OMAPL138/AM18xx.


The performance numbers are captured using the following:

  1. NOR PART Number: Intel PC28F640P30T85
  2. File System = JFFS2
  3. NOR partition was mounted with async option.


SPI Flash Driver[edit]

Abstract

This chapter describes the SPI flash driver architecture, driver features and performance numbers (throughput and CPU load).

Introduction[edit]

SPI Flash driver is implemented as block driver and compliant with standard MTD driver. It supports various flash devices. The SPI driver creates device node for user space access (example, /dev/mtd1).

SPI Driver.png

Driver Features[edit]

  • DMA and PIO modes are supported.

Features Not Supported[edit]

None

Constraints[edit]

None

Supported System Calls[edit]

Supports the system call support proivided by MTD interface viz. open(), close(), read(), write(), ioctl()

Performance Benchmarks[edit]

Performance numbers will be provided later

MMC/SD Driver[edit]

Abstract

This chapter provides details on MMC/SD driver along with throughput and CPU load numbers.

Introduction[edit]

The MMC controller provides an interface to external MMC cards that follow the MMC specification v4.0. The MMC driver is implemented as a block driver. Block device nodes(such as /dev/mmcblockp1, /dev/mmcblockp2) are created for user space access.

Mmcsd Driver.png

Driver Features[edit]

The driver supports the following features:

  1. MMC/SD native protocol command/response set
  2. Single/multiple block data transfers
  3. Linux file system and generic MMC layer abstract details of block devices (MMC)
  4. High-speed (SDv1.1) and High Capacity (SDv2.0) cards
  5. Support for 1/4 bit modes
  6. Support for card detect and Write protect features
  7. DMA and polled mode for data transfer operations

Features Not Supported[edit]

  1. Support for 8-bit mode of operation.
  2. SDIO - WLAN support
  3. SPI mode of operation

Constraints[edit]

  1. MMC/SD cards should not be removed when the mount operation is in progress. If done so, data integrity cannot be guaranteed.

Supported System Calls[edit]

open(),close(),read(),write()

Supported IOCTLs[edit]

None

Performance and Benchmarks[edit]

IMPORTANT
The performance numbers can be severely affected if the media is mounted in sync mode. Hot plug scripts in the filesystem mount removable media in sync mode to ensure data integrity. For performance sensitive applications, umount the auto-mounted filesystem and re-mount in async mode.


The performance numbers were captured using SDHC Card (SanDisk Extreme III, 4GB)

Performance using EXT2 file system[edit]

Write performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 8.80 9.33 9.21 9.43 52.02 48.70 53.83 51.44
256 100 8.36 8.79 8.45 8.77 50.40 50.00 49.47 52.26
512 100 8.73 9.31 9.28 9.38 53.88 50.76 54.44 49.37
1024 100 8.98 9.27 9.27 9.55 52.79 48.41 52.97 50.64
5120 100 8.71 9.34 9.44 9.57 54.42 51.52 51.71 50.41


Read performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 13.81 14.28 13.66 14.08 43.48 38.28 47.14 36.02
256 100 13.53 14.24 13.73 14.45 42.38 33.42 44.04 35.26
512 100 13.66 14.41 13.71 14.44 44.39 36.04 45.23 36.04
1024 100 13.69 14.17 13.74 14.41 43.47 32.57 43.91 35.35
5120 100 13.78 14.27 13.61 14.26 44.61 33.65 45.32 37.14


Performance using VFAT file system[edit]

Write performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 7.78 8.36 7.42 7.84 56.40 56.07 58.75 54.46
256 100 7.48 8.33 7.59 7.98 58.61 54.89 59.88 56.45
512 100 7.53 8.19 7.49 8.13 58.20 56.70 59.48 55.48
1024 100 7.41 8.29 7.64 8.05 56.95 54.08 59.97 54.65
5120 100 7.55 8.21 7.58 8.15 57.85 52.98 58.09 56.85


Read performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 13.46 14.94 13.58 15.23 48.91 35.90 44.49 35.27
256 100 13.11 14.51 13.67 13.69 47.31 33.66 44.86 33.51
512 100 12.90 15.12 13.65 13.56 41.57 35.06 45.19 36.43
1024 100 12.95 15.12 13.72 13.45 49.07 35.79 44.52 39.41
5120 100 13.14 15.04 13.9 13.48 53.45 35.15 45.54 35.86


UART Driver[edit]

Abstract

This chapter provides details on UART driver.

Introduction[edit]

The UART driver is implemented as a serial driver, and can be accessed from user space as /dev/ttyS2.

Uart.png

Driver Features[edit]

The driver supports the following features:

  1. Only UART2 is physically available on EVM board

Features Not Supported[edit]

  • None

Constraints[edit]

None

Supported System Calls[edit]

open(),close(),read(),write(),ioctl()

Supported IOCTLs[edit]

Constant Description
TIOCGSERIAL Gets device parameters from the UART (example, port type, port num, baud rate, base divisor, and so on.
TIOCSSERIAL Sets UART device parameters (example, port type, port num, baud rate, base divisor, and so on)

Performance and Benchmarks[edit]

None


I2C Driver[edit]

Abstract

This chapter provides details on I2C driver.

Introduction[edit]

The I2C peripheral is compliant with the Philips Semiconductor I2C-bus specification version 2.1. The I2C driver is implemented as a serial driver. The I2C driver can be accessed from the user space as /dev/i2c/0.

File:I2c.png

Driver Features[edit]

The driver supports the following features:

  1. 7-bit addressing mode
  2. Fast mode
  3. Interrupt mode

Features Not Supported[edit]

  1. 7-bit and 10-bit addressing combined format is not supported
  2. DMA mode is not supported

Constraints[edit]

  • None

Supported System Calls[edit]

open(),close(),read(),write(),ioctl()

Supported IOCTLs[edit]

Constant Description
I2C_SLAVE_FORCE Changes slave address. Slave address is 7 or 10 bits. This changes the address, even if it is already considered.
I2C_TENBIT 7- or 10-bit address. (Value = 0 for 7 bits; value != 0 for 10 bits.)
I2C_FUNCS Gets the adapter functionality
I2C_RDWR Combined R/W transfer (one stop only)

Performance and Benchmarks[edit]

None


EDMA Driver[edit]

Abstract

This chapter provides details on EDMA driver along with throughput and CPU load numbers.

Introduction[edit]

The EDMA controller handles all data transfers between the level-two (L2) cache/memory controller and the device peripherals. On DA850/OMAPL138 EDMA has 2 CC instances where as the other SoCs have one instance. Each EDMA instance supports up to 32-dma channels and 8 QDMA channels. The EDMA consists of a scalable Parameter RAM (PaRAM) that supports flexible ping-pong, circular buffering, channel-chaining, auto-reloading, and memory protection. The EDMA allows movement of data to/from any addressable memory spaces, including internal memory (L2 SRAM), peripherals, and external memory.

The EDMA driver exposes only the kernel level API's. This driver is used as a utility by other drivers for data transfer.

Driver Features[edit]

The driver supports the following features:

  1. Request and Free DMA channel
  2. Programs DMA channel
  3. Start and Synchronize with DMA transfers
  4. Provides DMA transaction completion callback to applications
  5. Multiple instances of EDMA driver on a single processor

Features Not Supported[edit]

  1. QDMA is not supported.
  2. Reservation of resources (channels and PaRAMs) for usage from DSP is not supported.

Constraints[edit]

None

Supported System Calls[edit]

None

Supported IOCTLs[edit]

None

Performance and Benchmarks[edit]

NA


Watchdog(WDT) Driver[edit]

Abstract

This chapter provides details on Watchdog timer driver.

Introduction[edit]

DaVinci SoCs have a 64-bit watchdog timer which can be used to reset the hardware in case of a software fault. Once the /dev/watchdog is opened, it will reboot the system unless a user space daemon resets the timer at regular intervals within a certain timeout period. The WDT driver is registered as a misc device. Default timeout of this driver is 60 seconds.

Wdt.png

Driver Features[edit]

The driver supports the following features:

  1. Supports IOCTLs to set/get the timeout value, ping the watchdog & query the watchdog structure info.
  2. Driver can be built as a loadable module and inserted dynamically.

Features Not Supported[edit]

  • None

Constraints[edit]

  1. Once /dev/watchdog is opened, closing it doesn't disable the watchdog

Supported System Calls[edit]

open(), close(), write(), read()

Supported IOCTLs[edit]

Constant Description
WDIOC_GETSUPPORT This ioctl returns "struct watchdog_info", which tells what the device can do
WDIO_KEEPALIVE This ioctl can be used to notify the watchdog timer that the user space application is alive
WDIO_SETTIMEOUT Watchdog timeout or margin can be dynamically changed using this ioctl
WDIO_GETTIMEOUT This ioctl returns the present watchdog timeout period in seconds

Performance and Benchmarks[edit]

None


USB Driver[edit]

Abstract

This chapter provides details on OHCI and MUSB drivers along with throughput and CPU load numbers.

This chapter describes the USB (EHCI and MUSB) driver architecture, features supported/not supported, constraints and performance numbers.

OHCI Controller[edit]

Driver Features[edit]

The driver supports the following features

  1. Human Interface Class (HID)
  2. Mass Storage Class (MSC)
  3. Hub Class
  4. USB Video Class (UVC)
  5. USB Audio Class (UAC)

Features Not Supported[edit]

All other classes not mentioned in the "Supported Features" section.

MUSB OTG controller[edit]

Description[edit]

The MUSB driver is implemented on top of Mentor OTG IP version 1.8 which supports all the speeds (High, Full and Low (host mode only)). On DA850/OMAP-L138, MUSB uses CPPI 4.1 DMA for all the transfers on other devices CPPI 3.0 DMA is used.

Driver Features[edit]

The driver supports the following features

Host Mode

  1. Human Interface Class (HID)
  2. Mass Storage Class (MSC)
  3. Hub Class
  4. USB Video Class (UVC)
  5. USB Audio Class (UAC)

Gadget mode

  1. Mass Storage Class (MSC)
  2. USB Networking - RNDIS/CDC

Features Not Supported[edit]

OTG

USB Mass Storage Class Host Driver[edit]

Driver Features[edit]

The driver supports the following feature

  1. DMA mode
  2. PIO mode

Features Not Supported[edit]

None


Constraint[edit]

None

Supported System Calls[edit]

open(), close(), read(), write(), ioctl()

Supported IOCTLS[edit]

None

Performance Benchmarks[edit]

IMPORTANT
For Mass-storage applications, the performance numbers can be severely affected if the media is mounted in sync mode. Hot plug scripts in the filesystem mount removable media in sync mode to ensure data integrity. For performance sensitive applications, umount the auto-mounted filesystem and re-mount in async mode.


USB MSC (MUSB) Host mode DMA EXT2 File System Performance[edit]

USB-MSC MUSB Host-DMA-Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 19.69 23.73 17.82 21.03 98 93 98.6 98.2
500 100 20.17 24.4 18.09 21.49 99 96 99 100
1024 100 20.38 24.42 18.20 21.56 99 56 71.7 99.3
5120 100 19.5 24.8 18.08 21.32 97 99 99.6 99.8


USB-MSC MUSB Host-DMA-Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 19.69 21.41 18.12 21.25 98.6 54.4 74.01 60.12
500 100 18.36 22.06 17.86 18.09 67.0 56.9 70.79 64.13
1024 100 18.02 21.76 18.32 21.32 62.7 58.4 71.78 57.78
5120 100 18.17 21.76 17.98 21.26 66.9 58.4 72.90 62.8


The performance numbers are captured using the following.

  1. Hard disk: Mobile Disk
  2. File format: ext2

USB MSC (MUSB) Host mode DMA VFAT File System Performance[edit]

USB-MSC MUSB Host-DMA-Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 11.54 13.31 10.26 11.90 80.11 72.78 79.49 75.0
500 100 11.37 13.59 10.44 11.80 79.2 72.6 81.3 69.2
1024 100 11.57 13.46 10.43 11.92 79.7 72.47 79.94 73.8
5120 100 11.70 13.20 1010 11.94 79.2 61.9 81.7 74.4


USB-MSC MUSB Host-DMA-Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz 300 MHz 456 MHz
100 100 17.18 19.62 16.98 11.9 71.8 65.0 70.32 71.6
500 100 17.12 19.56 16.86 11.80 70.1 59.4 73.4 69.2
1024 100 17.05 19.70 17.18 11.92 70.2 59.4 78.2 73.8
5120 100 17.13 19.53 16.72 18.76 69.1 61.9 69.6 68.0


The performance numbers are captured using the following.

  1. Hard disk: IOMEGA USB HDD 
  2. File format: VFAT



USB Mass Storage Class Slave Driver[edit]

Description[edit]

This figure illustrates the stack diagram of the system with USB File Storage Gadget driver

USBSlaveStorage.PNG

Driver Features[edit]

The driver supports the following feature

  1. DMA mode
  2. PIO mode
  3. File backed storage driver was tested with SD media as the storage medium

Features Not Supported[edit]

None

Constraint[edit]

None

Supported System Calls[edit]

NA

Supported IOCTLS[edit]

NA

Performance Benchmarks[edit]

USB Slave-DMA Performance[edit]

USB Slave-DMA-Write Performance values
Bytes Transferred (MB)'MicroSD Trascend as storage device' Number of files transferred Total Bytes transferred (MB)
Data Rate (MB/sec)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz
500 1 500 2.0 2.0 2.0 2.5


USB Slave-DMA-Read Performance values
Bytes Transferred (MB)'MicroSD Trascend'as storage device' Number of files transferred Total Bytes transferred (MB)
Data Rate (MB/sec)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz
500 1 500 5.5 6.6 5.5 7.0


The performance numbers are captured using the following.

  1. For OMAPL137 "Trascend MicroSD" Used as storage device
  2. File format: vfat on Windows XP

USB CDC/RNDIS Slave Driver[edit]

Description[edit]

The CDC RNDIS gadget driver that is used to send standard Ethernet frames using USB. The driver will create an Ethernet device by the name usb0.

UsBSlaveEthenet.PNG

Driver Features[edit]

The driver supports the following feature

  1. DMA mode
  2. PIO mode
  3. 10/100 Mbps speed.

Features Not Supported[edit]

None

Constraint[edit]

None

Supported System Calls[edit]

open(), close(), read(), write(), ioctl()

Supported IOCTLS[edit]

None

Performance Benchmarks[edit]

Performance benchmarks were collected using the Iperf tool and default options were used to collect the throughput numbers.

DA850/OMAP-L138[edit]

USB CDC-DMA Performance[edit]

USB CDC-DMA Performance values - Client
TCP Window Size(in KBytes) Interval (in Seconds) Bandwidth (Mbits/Sec)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz
16 10 40.6 49.5 38.1 48.6
32 10 40.6 49.6 38.8 48.7
64 10 40.7 49.9 38.7 48.8
128 10 40.6 49.7 38.9 48.5


USB RNDIS-DMA Performance[edit]

USB RNDIS-DMA Performance values - Client
TCP Window Size(in KBytes) Interval (in Seconds) Bandwidth (Mbits/Sec)
DA850/OMAP-L138/AM18xx DA830/OMAP-L137/AM17xx
300 MHz 456 MHz 300 MHz 456 MHz
16 10 33.2 39.2 33.0 38.1
32 10 33.0 39.7 32.9 38.8
64 10 32.6 40.2 32.8 38.7
128 10 33.3 40.0 32.9 38.9


USB Human Interface Device (HID) Driver[edit]

Description[edit]

The event sub system creates /dev/input/event* devices with the help of mdev.

Driver Features[edit]

The driver supports the following feature

  1. DMA mode
  2. PIO mode
  3. USB Mouse and Keyboards that conform to the USB HID specifications

Features Not Supported[edit]

None

Constraint[edit]

None

Supported System Calls[edit]

NA

Supported IOCTLS[edit]

NA

Performance Benchmarks[edit]

NA

USB Isochronous Driver[edit]

Description[edit]

USB camera, speaker and mic uses isochronouse transfers. USB Video Class (UVC) is used by most of the USB cameras to capture image.

Driver Features[edit]

The driver supports the following feature

  1. DMA mode
  2. PIO mode
  3. Support for USB Audio and video class(UVC class)

Features Not Supported[edit]

None

Constraint[edit]

None

Supported System Calls[edit]

NA

Supported IOCTLS[edit]

NA

Performance Benchmarks[edit]

NA

USB OTG Driver[edit]

Description[edit]

MUSB controller on DaVinci supports USB On The Go (OTG). OTG protocol enables runtime role switch between USB host and device. This is achived using Session Request Protocol (SRP) and Host Negotiation Protocol (HNP). OTG driver is tested with OPT (OTG Protocol Tester).

Driver Features[edit]

The driver supports the following feature

Features Not Supported[edit]

OTG

Constraint[edit]

None

Supported System Calls[edit]

NA

Supported IOCTLS[edit]

NA

Performance Benchmarks[edit]

NA


SATA[edit]

Description[edit]

SATA peripheral is AHCI Ver.1.1 spec compliant peripheral.  It supports SATA1 (150MBps) and SATA 2 (300MBps) speeds over one SATA port.  Port Multiplier support is available in the SATA controller.  The controller can support drives upto UDMA-133 speeds.

Driver Features[edit]

Registers as a SCSI controller with the Linux SCSI Subsystem.  SATA devices get registered as SCSI devices and can be accessed as "/dev/sd{*}" devices.

  • Port Multiplier support
  • CD/DVD support

Driver Features Not Supported[edit]

None.

Constraint[edit]

None

Supported System Calls[edit]

NA

Supported IOCTLS[edit]

NA

Performance Benchmarks[edit]

SATA - ext2 File System Performance[edit]

SATA - Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
300 MHz 456 MHz 300 MHz 456 MHz
100 100 21.5 26.6  99 99 
500 100 21.5  26.6 99  99 
1024 100 21.6  26.6 99  99 
5120 100 21.4 26.4 99 99


SATA - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
300 MHz 456 MHz 300 MHz 456 MHz
100 100 36.6  44.6  98  98 
500 100 37.3 44.5  99  99
1024 100 37.2 44.6 98 99 
5120 100 36.7  43.6  99  99 


The performance numbers are captured using the following.

  1. SATA HDD - Seagate Baracuda 7200 RPM 500GB drive
  2. File format: ext2


Video Port Interface (VPIF)[edit]

Abstract

This chapter provides details on Video Port Interface (VPIF) used for video display and capture.

Description[edit]

This section describes the Video Port Interface (VPIF) is a Linux V4L2 driver. It uses v4l2-subdev interface to interact with the encoders and decoders. On DA850/OMAP-L138/AM1808 EVM, VPIF channel 0 and channel 1 are used for capture and channel 2 is used for display. Channel 0 takes in composite input and Channel 1 is for S-Video input. There are 2 TVP5146 decoders interfaced, one for each channel. Channel 2 is used for output. One ADV7343 encoder is connected to it and output is either Composite or S-Video depending on the output type chosen.

Driver Features[edit]

  1. Supports Composite Video input and output
  2. Supports S-Video input and output
  3. Supports V4L2 driver model for video planes
  4. Supports NTSC and PAL standards
  5. Supports SBGGR8 and NV16 color formats for capture and NV16 color format for display.

Driver Features Not Supported[edit]

  1. Framebuffer (fbdev) interface is not supported.
  2. Raw Capture is not supported
  3. VBI data on display and capture is not supported
  4. HD resolutions are not supported

Performance Benchmarks[edit]


Video Display Performance
Resolution Frame Rate CPU Load (in %)
300 MHz 456 MHz 300 MHz 456 MHz
NTSC(720x480) 30 30 0.29  0.29 
PAL(720x574) 25  25  0.30 0.30 


Video Capture Performance
Resolution Frame Rate CPU Load (in %)
300 MHz 456 MHz 300 MHz 456 MHz
NTSC(720x480) 29.99  29.99  31.87  28.62 
PAL(720x574) 25.023  25.023  25.06  25.07 


McBSP[edit]

Description[edit]

Multi-channel Buffer Serial Port (McBSP) peripheral is primarily used for serial data transfer like in the case of audio interfaces. McBSP supports DMA mode of transfer and hence is suitable for real-time audio applications. The McBSP driver provides APIs to the programmer to control McBSP.

Driver Features[edit]

  1. The driver is an API driver.
  2. Supports multiple instances of the peripheral.
  3. Supports master transmitter and slave receiver operation.
  4. Supports multi-channel selection mode of operation.
  5. Supports configuration of word length, frame length, sample frequency.

Driver Features Not Supported[edit]

Slave transmitter, master receiver combination.

Constraint[edit]

The test setup consists of Interposers connecting two EVMs with the necessary connections wired. Using this setup, the maximum frame length that has been tested is 32. Beyond this the test results are not stable.

Supported System Calls[edit]

NA

Supported IOCTLS[edit]

NA

Performance Benchmarks[edit]

NA

E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article DaVinci PSP 03.20.00.13 Device Driver Features and Performance Guide here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity