NOTICE: The Processors Wiki will End-of-Life in December of 2020. 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.

DM814x C6A814x AM387x PSP 04.01.00.05 Feature Performance Guide

From Texas Instruments Wiki
Jump to: navigation, search
{{#switchcategory:MSP430=<McuHitboxHeader/>|C2000=<McuHitboxHeader/>|Stellaris=<McuHitboxHeader/>|TMS570=<McuHitboxHeader/>|MCU=<McuHitboxHeader/>|MAVRK=<MAVRKHitboxHeader/>|<HitboxHeader/>}}
TIBanner.png
DM814x C6A814x AM387x 04.01.00.05 Feature & Performance Guide
Linux PSP
IMPORTANT

DM816x refers to DM816x/AM389x devices unless specified.
DM814x refers to DM814x/AM387x devices unless specified.
DM81xx refers to both DM816x, DM814x and DM813x.

Important
This datasheet is applicable for 04.01.00.05 release only.



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]

All performance numbers provided in this document are gathered using DM8168 EVM with DDR3 configured at 400 MHz clock (effective 800MHz data rate).

About This Manual[edit]

This document provides an overview and performance data for each of the device drivers which are part of the Linux PSP package supporting DM8148 EVM (Base board). Note that only a subset of the drivers may have actually been fully tested and verified in the package you are using. Please refer to the release notes provided with the package for information on which of the drivers have actually been verified. In the rest of the document, we will refer this setup as DM8148 EVM.

If You Need Assistance[edit]

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

U-Boot[edit]

Hardware Related Info[edit]

U-Boot currently does the bare minimum configuration needed to boot the kernel. The following table lists various resources enabled by the ROM code + U-Boot running on the host ARM (that is, Cortex A8).

Resource Specifics Notes
OCMC RAM OCMC0 1st stage U-Boot runs out of OCMC0
Control module NA Needs to be enabled prior to enabling other modules.
Clocks/PLL Setup Modena (A8), L3, DDR, SATA, DSP, DSS, IVA, ISS, USB
UART UARTs 0-5 UART0 is available as console on base board.
Timers Timer1 Used for timekeeping purpose
RAM Both the EMIFs Non-interleaved configuration
I2C I2C0
SPI
Module enabled.
EMACSW Ethernet port (with internal switch) Used for DHCP, TFTP load of kernel (and/or) filesystem images.
NAND Whole Base EVM has 256MiB NAND

Linux Kernel[edit]

Module/Subsystem Usage[edit]

Following table covers various onchip modules/subsystems enabled and used in U-Boot and Kernel. It also lists module status on reset. Note that there may be a few modules which are enabled but not used currently but will be used in future.

The table uses following conventions for enabled status:

  • BOOTCFG - Module is enabled depending upon boot mode
  • YES - Module is enabled always and is critical for functioning (should never be turned off).
  • CONFIG - Module will be enabled depending upon build time or run time configuration (e.g., SATA module is enabled if SATA is enabled in kernel build configuration, UART1 is enabled if 'ttyO1' is passed as console through kernel command line). Note that there may be many modules included in default build configuration and thus they will be enabled by default (e.g., EMACSW), though these can be disabled by disabling respective configuration in build.
  • KEEP - Module already enabled and kept as is. Note that, except for Control Module, eFuse and EMIFs, in most of the other cases, this means that the corresponding module is not currently used and was enabled by the component which executed earlier. This is, module enabled status 'KEEP' in Kernel means it was enabled by U-Boot (or boot time) but kernel doesn't touch it.
  • NO - Module is not used and is not enabled
Module/Subsystem Enabled on Reset? Enabled in U-Boot? Enabled in Linux?
Control Module YES KEEP KEEP
eFuse YES YES KEEP
OCMC0 & 1 BOOTCFG YES KEEP
GPIO0 NO YES KEEP
GPIO1 NO NO NO
EMIF0 & 1 NO YES KEEP
UART0-2 BOOTCFG YES CONFIG
UART3-5 NO NO CONFIG
Timer1 NO YES YES
Timer2 NO NO YES
Timer3 NO NO CONFIG
Timer4 to 8 NO NO NO
GPMC BOOTCFG YES CONFIG
EDMA TPCC NO NO YES
EDMA TPTC NO NO YES
SPI BOOTCFG YES KEEP
I2C0-2 NO YES CONFIG
I2C1-3 NO NO NO
EMACSW BOOTCFG YES CONFIG
USB NO NO CONFIG
SATA NO NO CONFIG
PCIe BOOTCFG NO CONFIG
SGX NO NO NO
IVAHD NO NO NO
Ducati NO NO CONFIG
MMU NO NO NO
MMU DATA NO NO NO
DSP NO NO CONFIG
Spinlock NO NO CONFIG
Mailbox NO NO CONFIG
HDMI NO NO NO
McASP0 NO NO CONFIG
McASP2-5 NO NO NO
McBSP NO NO NO
MMC0 NO NO NO
MMC1 BOOTCFG YES CONFIG
MMC2 NO NO NO

Hardware Resources Reserved for Kernel[edit]

Following table lists various resources owned and used exclusively by kernel (that is, Cortex A8). Care must be taken not to share these across other processors. Of course, there can be a kernel module/driver which monitors the sharing - this is particularly applicable for shared buffers in RAM - but the control should still remain with kernel.For modules having multiple instances, numbering is assumed to be from '0'.

Resource Specifics Notes
UART

UART0

This is configurable through kernel command line ('bootargs') and is board dependent. On Base board, UART0 is used as console.
Timers

Timer1, Timer2

Timer1 - System Timer, Timer2 - Free Running
RAM 0x80000000 - 0x88000000 The RAM size allocated for kernel is configurable through boot argument 'mem=' passed to kernel during boot. The start address (0x80000000) is fixed. Also note that it is possible to map RAM region beyond this range into kernel virtual memory space using kernel drivers/modules. Multiple 'mem=' arguments can be passed to have the system RAM spanned across holes in between. Please refer User Guide for details
I2C I2C0 Refer board reference document/schematics for more details.
EMACSW
Has internal Ethernet switch.
NAND Whole Base EVM has 256MiB NAND.
EDMA

4 to 47,

52 to 54

Peripheral Only: 4 to 31, 52 to 54

Mem to Mem: 32 to 47

OCMC0

0x40300000 - 0x4031FFFF

OCMC 0 will be used by ROM Code and U-boot. Once Linux kernel boots, OCMC0 is free and kernel can use it. If OCMC0 should not be used to load u-boot if loaded using CCS.


Kernel Virtual Memory Layout
[edit]

The default TI814X kernel configuration, with "mem=128M" passed as boot argument, uses following Virtual Memory laout:

Memory: 78MB = 78MB total
Memory: 73476k/73476k available, 57596k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xc8800000 - 0xf8000000   ( 760 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0037000   ( 188 kB)
      .text : 0xc0037000 - 0xc04a2000   (4524 kB)
      .data : 0xc04a2000 - 0xc04e5140   ( 269 kB)

Please note following points:

  • Default kernel build is set up with 3G/1G split for User/Kernel space.
  • The vmalloc and lowmem are dependent on RAM available to kernel (as specified by 'mem=<size-in-MB>M' boot argument). As you provide more memory for kernel to map, the vmalloc space will be lowered. Vice versa is true when vmalloc region is changed by passing 'vmalloc=<size-in-MB>M' argument
  • RAM size more that 768M will be truncated to maintain minimum vmalloc at 120MB
  • It should be possible to allow larger memory into kernel space by changing User/Kernel split to 2/2 or 1/3. Please note that these are NOT TESTED and may lead to unpredictable behavior.
  • Alternatively, "High Memory" support in kernel (CONFIG_HIGHMEM) can be enabled to accommodate larger physical memory. Note again that, this is an EXPERIMENTAL feature and may lead to stability and performance issues.

Note: Around 50MB of RAM is reserved for FB driver by default hence you see total memory as 78MB when passing 'mem=128M'.

Boot-time measurement[edit]

For boot-time measurement the following setup was used

  • 2-Stage SD boot (binaries picked from the release package)
  • Kernel image of size 2.3MB (image picked from the release package)
  • Sandisk Extreme 3 Class-6 4GB SD card
  • Filesystem on the SD card - 14MB

The kernel image used had the following features enabled

  • NAND driver
  • Block devices
  • SCSI devices
  • SATA drivers
  • Network device support
  • I2C support
  • SPI support
  • GPIO support
  • WDT support
  • Sound card support
  • HID devices
  • USB support
  • MMC/SD/SDIO support
  • Loadable module support
  • Filesystem support for ext2, ext3, JFFS2 and NFS

The following was the kernel command line passed

 console=ttyO0,115200n8 root=/dev/mmcblk0p2 mem=128M init=/bin/sh rootwait

The total boot-time (ignoring the boot delays in the 2 stages of U-Boot) is ~11.79 secs

The break-up of the boot-time is as given below:

  • Booting the compressed kernel (calculated from the time U-Boot displays "## Booting..." to the prompt) :4.82 secs
  • Reading the 2.3MB uImage from SD card : 3.59 secs
  • Misc time in U-Boot : 3.38 secs

PSP Linux Drivers[edit]

This section provides brief overview of the device drivers supported in the Linux PSP release based on Linux OMAP git tree.

Note: The constraints may vary across product releases. Please refer to the Release Notes accompanying the release for an updated list of constraints.

Boot modes supported[edit]

Green colored box in the table below means that the particular boot mode is supported on the device in the release.

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.


TI814X Linux PSP Supported Boot Modes
Boot Mode DM8148 EVM
NAND Flash Yes
NOR Flash No
SPI EEPROM Yes
SD Yes
EMAC Boot No
UART Boot Yes (UART0)
PCIe Boot Yes (Verified from DM816x RC only)


Device driver list[edit]

Device Driver List
Peripheral Description Linux driver type
Audio (McASP) Audio record and playback ALSA SoC
Ethernet Transmit/receive network data. Supports Auto negotiation with 10/100 Mbps link speed Netdev
I2C Inter-IC Communication Character
MUSB Host Supports MSC and HID classes USB HCD
NAND Flash Flash storage system MTD Character and Block
UART Serial Communication Interface Character
SATA Storage Block Device
MMC/SD Interface to MultiMedia Secure Digital cards Block Device
Watchdog Interface to h/w Watchdog /dev/watchdog

Driver DMA usage[edit]

TI814x peripheral driver DMA usage
Driver DMA usage
Audio (McASP) EDMA
Ethernet Internal DMA
MUSB Host Internal DMA
NAND Flash None
UART None
I2C None
SATA Internal DMA
MMC/SD EDMA
SPI None

SATA Driver[edit]

SATA controller is AHCI Ver.1.1 spec compliant . It supports SATA1 (150MBps) and SATA 2 (300MBps) speeds. Port Multiplier support is available in the SATA controller. The controller can support drives upto UDMA-133 speeds. Please refer PSP SATA FAQ for more information.

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.

The driver supports the following features:

  1. CD/DVD support
  2. HDD
  3. Port Multiplier support

[Linux Libata feature table] for more details.

Features Not Supported[edit]

  • Power Management : Though supported, validation is still pending.

Constraints[edit]

Supported System Calls[edit]

All Linux ATA/SCSI system calls related to SATA

Supported IOCTLs[edit]

Supports IOCTLS available in Linux SCSI and ATA frameworks and which are applicable for SATA. Refer kernel source or documentation for details.

Performance and Benchmarks[edit]

Please read the SATA Test Setup section before proceeding.

Test Parameters[edit]

Test Parameters
Silicon Revision 2.1
EVM
DM8148 EVM S/N MS_CBB_DDR3_PG2_S_A1_024
DDR
DDR3 DIMM, 400 Mhz data rate
LFTB version 02.00.00.04
Number of SATA Ports
1
Port 0 - HDD

Seagate Barracuda 7200.11 RPM 500GB

(~120MBytes/sec sustained data rate)

Performance Data[edit]

Below tables were filled by running the performance test suite mentioned in SATA Test Setup section.

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 %)
100 100 77.55  42.96
256 100 69.38 39.07 
512 100 69.84  39.33
1024 100 67.08  38.22
5120 100 70.45  39.60 


SATA - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 113.58 65.59
256 100 107.26 49.48 
512 100 114.10 67.03
1024 100 110.37 62.77 
5120 100 113.47 56.52


SATA - vfat 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 %)
100 100 51.33 58.05
256 100 53.19 61.11
512 100 52.10 59.90
1024 100 53.87 62.05
5120 100 50.85 57.77


SATA - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 107.05 69.70
256 100 107.90 64.95
512 100 107.90 71.13
1024 100 106.99 71.43
5120 100 107.24 60.82


ALSA SoC Audio Driver[edit]

This section an overview of the ALSA SoC audio driver features along with the throughput and CPU load numbers. For the architecture, installation, basic usage and sample applications (if any) please refer to the driver user guide.

Driver Features[edit]

The driver supports the following features:

  1. Supports AIC3106 audio codec (on DM8148 base EVM)
  2. Supports audio in stereo mode
  3. Supports simultaneous playback and record (full-duplex mode).
  4. Supports mixer interface for the audio codec

Features Not Supported[edit]

  1. OSS based applications, which use ALSA-OSS emulation layer, are not supported.
  2. Formats such as TDM, Left and Right Justified are currently not supported.
  3. Synthesizer and midi interfaces are not supported.

Constraints[edit]

  1. 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.
  2. Sampling frequencies for playback and capture streams should be same.
  3. The audio driver does not allow opening the same stream (playback/capture) multiple times.

Supported System Calls[edit]

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

Supported IOCTLs[edit]

NA

Performance and Benchmarks[edit]

Test setup:

  1. Access type - RW_INTERLEAVED
  2. Channels - 2
  3. Format - S16_LE
  4. Period size - 64


Audio capture
Sampling Rate (in Hz) Duration (in secs) Bitrate (in bits/sec) CPU Load (in %)
8000 327.65 256025 0.31
11025 237.75 352835 0.40
16000 163.82 512050 0.56
22050 118.87 705669 1.12
24000 118.87 705669 1.12
32000 81.91 1024100 1.59
44100 59.44 1411338 2.13
48000 54.61 1536149 2.68
88200 29.72 2822671 4.45
96000 27.30 3072292 6.87


Audio playback
Sampling Rate (in Hz) Duration (in secs) Bitrate (in bits/sec) CPU Load (in %)
8000 327.52 256129 0.23
11025 237.65 352977 0.28
16000 163.76 512257 0.45
22050 118.83 705954 0.63
24000 118.83 705954 0.67
32000 81.88 1024513 1.59
44100 59.41 1411907 2.18
48000 54.59 1536769 2.37
88200 29.71 2823809 4.36
96000 27.29 3073534 6.72

Ethernet Driver[edit]

This section provides an overview of the Ethernet driver features along with throughput and CPU load numbers. For the architecture, installation, basic usage and sample applications (if any) please refer to the driver user guide.

Driver Features[edit]

The driver supports the following features:

  1. 10/100/1000 Mbps mode of operation.
  2. Auto negotiation.
  3. Support for multicast and broadcast frames.
  4. Promiscuous mode of operation.
  5. Linux NAPI support
  6. Only one port on the Baseboard is supported

Features Not Supported[edit]

  1. Second switch port
  2. Switch mode of operation

Constraints[edit]

NA

Supported System Calls[edit]

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

Performance and Benchmarks[edit]

Ethernet Port0 TCP - 1Gbps Mode Rx Performance
TCP Window Size
(in KBytes)
Bandwidth - TI814x
(in Mbits/sec)
TransferSize - TI814x
(in GBytes)
CPU Load (in %)
16 364 2.55 75
32 424 2.96 87
64 441 3.08 90
128 438 3.06 90
256 437 3.05 91


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

  • iperf version 2.0.4
  • On the DUT iperf is invoked in server mode  : "-s -w 256k"
  • On PC Host invoke iperf in the client mode  : "-c <server ip> -w <window size> -t60"
  • The transfers are measured over a duration of 60Secs
  • Cross cable is used to measure performance.
  • Speed is set to 1000Mbps
  • Root filesystem mounted from NAND (JFFS2).


Ethernet Port0 TCP - 1Gbps Mode Tx Performance
TCP Window Size
(in KBytes)
Bandwidth - TI814x
(in Mbits/sec)
TransferSize - TI814x
(in GBytes)
CPU Load (in %)
16 301 2.11 100
32 302 2.11 100
64 304 2.12 100
128 303 2.12 100
256 302 2.11 100


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

  • iperf version 2.0.4
  • On the DUT iperf is invoked in client mode  : "-c <server ip> -w <window size> -t60"
  • On PC Host invoke iperf in the server mode  : "-s -w 256k"
  • The transfers are measured over a duration of 60Secs
  • Cross cable is used to measure performance.
  • Speed is set to 1000Mbps
  • Root filesystem mounted from NAND (JFFS2).


NAND Driver[edit]

This section provides an overview of the NAND flash driver features along with throughput and CPU load numbers. For the architecture, installation, basic usage and sample applications (if any) please refer to the driver user guide.

Driver Features[edit]

The driver supports the following features:

  1. JFFS2 file system
  2. Supports Read/Write, Erase operations
  3. Bad Block Management
  4. Polled mode of transfer
  5. SLC NAND

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]

Please refer MTD Test Setup before proceeding.

NAND Write Performance[edit]

  • 0.60 MBytes/sec

NAND Read Performance[edit]

  • 3.3 MBytes/sec

NOTE: The filesystem performance tests are obtained by running LTD-DDT. The mount command in LTP-DDT is: "mount -t $FS_TYPE $DEV_NODE $MNT_POINT"
You can use the following url to access LTP-DDT scripts and test codes.
http://arago-project.org/git/projects/?p=test-automation/ltp-ddt.git;a=shortlog;h=refs/heads/next


USB Driver[edit]

This section gives an overview of the USB (MUSB) driver features supported/not supported, constraints and performance numbers.

MUSB OTG controller[edit]

The MUSB driver is implemented on top of Mentor controller IP which supports all the speeds (High, Full and Low). TI8148 USBOTG subsytem uses CPPI 4.1 DMA for all the transfers.

Features Not Supported[edit]

1. OTG support

Driver Features[edit]

The driver supports the following features

Host Mode

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

Gadget mode

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

USB Mass Storage Class Host Driver[edit]

Driver Features[edit]

The driver supports the following feature

1.DMA mode

2.PIO mode

Constraint[edit]

None

Supported System Calls[edit]

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

Supported IOCTLS[edit]

None

Performance Benchmarks (DMA mode)[edit]

       Setup : WesternDigital HDD (500GB) connected to usb0 port.
       File read/write performance data on usb0 port(WDD HDD) has been captured.
       LFTB Version 2.00.00.04 used for performance.

For Test setup details refer to usb-host-msc test setup

USB - ext2 File System Performance[edit]

USB - Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 21.85 16.91
256 100 22.41 16.56
512 100 22.57 17.03
1024 100 22.30 16.60
5120 100 22.39 17.31


USB - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 22.70 21.21
256 100 22.36 20.94
512 100 22.65 23.26
1024 100 22.61 21.26
5120 100 22.54 23.81


USB - vfat File System Performance[edit]

USB - Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 19.28 36.53
256 100 19.29 38.38
512 100 19.30 45.29
1024 100 19.34 43.70
5120 100 19.16 44.22


USB - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 20.83 23.31
256 100 20.96 24.14
512 100 20.78 23.26
1024 100 20.81 24.05
5120 100 20.86 22.80


The performance numbers are captured using the following.

  1. HDD - Western Digital 500GB drive


USB - ext2 File System Performance on simulataneous read/write on two HDD[edit]

       Setup : WesternDigital HDD (500GB) connected to usb0 port and Toshiba HDD connected to usb1 port.
       File read/write performance data on usb0 port(WDD HDD) has been captured while simulatenous
       file write is in progress on usb1 port(Toshiba HDD).
       LFTB Version 2.00.00.04 used for performance.
USB - Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 17.76 48.98
256 100 18.34 48.25
512 100 17.75 50.17
1024 100 18.19 48.22
5120 100 18.65 48.22


USB - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 18.80 54.55
256 100 18.56 67.5
512 100 19.56 54.71
1024 100 19.35 53.66
5120 100 18.73 56.66


USB - VFAT, File System Performance on simulataneous read/write on two HDD[edit]

       Setup : WesternDigital HDD (500GB) connected to usb0 port and Toshiba HDD connected to usb1 port.
       File read/write performance data on usb0 port(WDD HDD) has been captured while simulatenous
       file write is in progress on usb1 port(Toshiba HDD).
       LFTB Version 2.00.00.04 used for performance.
USB - Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 19.28 36.53
256 100 19.29 38.38
512 100 19.30 45.29
1024 100 19.34 43.70
5120 100 19.16 44.22


USB - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 20.83 23.31
256 100 20.96 24.14
512 100 20.78 23.76
1024 100 20.81 24.05
5120 100 20.86 22.80


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 SATA HDD 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]

    The performance numbers are captured in DMA Mode using SATA HDD as file storage 
    gadget media exposing as removable media to windows-xp over USB. The SATA HDD is 
    formatted using the NTFS on windows-xp.
    #SATA HDD used - Western Digital 500GB drive
    While insert g_file_storage.ko use the module parameter buflen set to 65536
    # insmod g_file_storage.ko file=/dev/sda buflen=65536 stall=0 removable=1

For test setup details refer to msc-device setup

USB Slave- DMA Write Performance values
Bytes Transferred (MB)'SATA HDD'as storage device Number of files transferred Total Bytes transferred (MB) Transfer Rate (MB/sec)
250 1 250 17


USB Slave- DMA Read Performance values
Bytes Transferred (MB)'SATA HDD'as storage device Number of files transferred Total Bytes transferred (MB) Transfer Rate (MB/sec)
250 1 250 25


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.


USB RNDIS-DMA Performance[edit]

    Setup : EVM as client and Linux Host PC as server
    command at EVM: iperf -c <window/linux host ip_adr> -w <8|16|32|64|128>K -t 60 -d
    command at Host: iperf -s

For test setup details refer cdc-rndis setup

USB RNDIS-DMA Performance values - Client
TCP Window Size(in KBytes) Interval (in Seconds) Bandwidth (Mbits/Sec)
8 60 132
16 60 110
32 60 115
64 60 127
128 60 128



USB(HIGHSPEED)CDC-DMA Performance[edit]

USB CDC-DMA Performance values - Client
TCP Window Size(in KBytes) Interval (in Seconds) Bandwidth (Mbits/Sec)
8 60 71
16 60 76.1
32 60 76.3
64 60 76.6
128 60 76.1


MMC/SD Driver[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.

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. MMC/SD card hot insertion

Features Not Supported[edit]

  1. 1-bit, 8-bit modes of operation.
  2. 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.

Please refer MMC/SD Test Setup before proceeding.

EXT2 file system[edit]

SD - Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 8.017694 9.08
256 100 9.057638 10.39
512 100 8.705183 8.93
1024 100 8.486333 9.04
5120 100 8.691412
8.34


SD - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 17.422018 21.29
256 100 17.415600 20.79
512 100 17.416433 18.65
1024 100 17.414839 18.21
5120 100 17.410116
13.67


The performance numbers were captured using the following:

  • SD Card (Sandisk Extreme, SDHC, Class 10, 4GB)
  • File System: ext2
  • Partition was mounted with async option

VFAT file system[edit]

SD - Write Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 9.085071 15.78
256 100 9.200367 17.19
512 100 9.256588 17.09
1024 100 9.117352 15.34
5120 100 8.979396 15.46


SD - Read Performance values
Buffer Size (in KBytes) Total Bytes Transferred (in MBytes) Transfer Rate (in MBytes/sec) CPU Load (in %)
100 100 16.634481 19.59
256 100 16.658936 21.11
512 100 16.683384 21.33
1024 100 16.658533 22.12
5120 100 16.710394 21.84


The performance numbers were captured using the following:

  • SD Card (Sandisk Extreme, SDHC, Class 10, 4GB)
  • File System: vfat
  • Partition was mounted with async option


[edit]

Video Display Driver[edit]

This section describes the Video Display driver architecture, driver features.

Description[edit]

The following digram showes the architecture of the Video display Driver

Vpss linux sw arch.png


Driver Featurs[edit]

  1. Support 1080p-60/1080p-50/1080P-30/1080I-60/1080I-50/720P-60/720P-50 mode display through HDMI VENC
  2. Support mux multiple graphics planes into single VENC
  3. Support Video PLL configuration
  4. Support Venc Clock source configuration
  5. Support VENC output configuraiton(digital data format, sync mode, analog output format)
  6. Support PAL/NTSC SVIDEO output through SD_VENC
  7. Support reshuffling display order
  8. Support Customized timing configuration for DVO1/DVO2 output.
  9. Support on-chip HDMI display together with HDMI Kernel Driver.

Features Not Supports[edit]

  1. EVM RF output is not supported
  2. EVM Composite output is not supported
  3. EVM VGA output is not support

Fbdev Driver[edit]

Frame-buffer Display Driver.

Driver Features[edit]

  1. Support 3 independent graphics planes
  2. Support RGB888/ARGB8888/RGBA8888/RGB565/ARGB1551/RGBA5551/RGBA4444/ARGB4444/ARGB6666/RGBA6666
  3. Support 0.25x-4x scaling
  4. Support boundbox blending
  5. Support global blending
  6. Support Pixel blending
  7. Support Pallette blending
  8. Support RGB888 color key mapping
  9. Support anti-flickering filter.
  10. Support wait for VSYNC and paning
  11. Support mmapped (driver allocated) buffers


Features Not Supports[edit]

  1. Rotation is not supported.
  2. Mirroring is not supported.
  3. Stencliling is not supported


Constrains[edit]

None

Supported System Calls[edit]

open(), close(), mmap(), munmap() and ioctl()

Performance Benchmarks[edit]


Please check HDVPSS Feature Performance Guide here  

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 DM814x C6A814x AM387x PSP 04.01.00.05 Feature 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 DM814x C6A814x AM387x PSP 04.01.00.05 Feature 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 DM814x C6A814x AM387x PSP 04.01.00.05 Feature Performance Guide here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article DM814x C6A814x AM387x PSP 04.01.00.05 Feature Performance Guide here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article DM814x C6A814x AM387x PSP 04.01.00.05 Feature Performance Guide here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article DM814x C6A814x AM387x PSP 04.01.00.05 Feature Performance Guide here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article DM814x C6A814x AM387x PSP 04.01.00.05 Feature 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 DM814x C6A814x AM387x PSP 04.01.00.05 Feature Performance Guide here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article DM814x C6A814x AM387x PSP 04.01.00.05 Feature 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

{{#switchcategory:MSP430=<McuHitboxFooter/>|C2000=<McuHitboxFooter/>|Stellaris=<McuHitboxFooter/>|TMS570=<McuHitboxFooter/>|MCU=<McuHitboxFooter/>|MAVRK=<MAVRKHitboxFooter/>|<HitboxFooter/>}}