A Brief  overview
===========================
LFTB - Linux Function Test Bench is a collection of test suites to test the linux driver functionaliy.


Platforms supported
================================

am3517  am37x  omap35x  am17x  am18x  ti816x ti814x

Platforms supported for FBDev
================================

dm644x, dm365, dm355, am18x, am17x, omap35x and am3517

Platforms supported for V4L2_capture and V4L2_Display
================================

dm646x, dm644x, dm365, dm355, am18x, omap35x and am3517

Platforms tested
================================

dm646x, dm644x, dm365, dm355, am18x, omap35x, am3517, am17x ti816x and ti814x

Steps to build & install
================
1)Enter following information in the USERDEFINES file (LFTB top directory)
    KERNEL_DIR  - Kernel path 
    TOOL_PREFIX - Tool chain path
    PLATFORM    - Platform
    INSTALL_DIR - Install directory where the package to be placed

NOTE: user can also specify KERNEL_DIR KERNEL_DIR PLATFORM INSTALL_DIR as part of command line argument Eg PLATFORM=ti816x

2)Issue the command - 'make ' to build all the supported test suites.
HOST$ make

The above steps will build the executable and place it in bin/<platform> directory for each test suite.

3)Issue the command - 'make install' to copy the required executables and scripts in the INSTALL_DIR
HOST$ make install

Step to clean
=============
1)'make clean' - Command to clean the created binaries.
HOST$ make clean

Steps to run
================
1)Boot the DUT using the uImage built from appropriate PSP release.
2)To Run all the automated testcases for a platform (all modules), change to automation/common directory and run the automation_script.sh
HOST$ cd automation/common
HOST$ ./automation_script.sh -plat <platform name> -type <all, sanity, func, modular> -dst_ip <ip> -src_ip <ip> -device_type <mmc/flash> 

Eg: ./automation_script.sh -plat ti816x -type all
NOTE1: for modular test case all the modules should be in the automation/common directory
NOTE2: -dst_ip,-src_ip are required if ethernet testcases are required as part of automation testing. -dst_ip is the IP address of host for ethernet tests (ping, iperf). -src_ip is EVM/Target IP address.
NOTE3: -device_type is applicable only for am18x platform as there is a limitation that only either
       nand/nor or mmc can be configured in the kernel at a time (due to pin muxing).
NOTE4: Following modules are supported as part of automation_script.sh

1. WDT
2. RTC
3. ALSA
4. EDMA
5. Filesystem
6. MTD
7. I2C


3)To run all the automated testcases for individual test suites, changes the directory to <module_test_suite>/scripts/common
Refer to the sample scripts module_tests_script.sh by executing with -help option. 
	
Eg. Usage:
./wdt_tests_script.sh -device -type -plat [-ko] [-h]
 device : Device-node interface, Possible values-/dev/watchdog
 plat   : platform. Possible values are - am18x/ am17x/ omap35x/am37x/ am3517/ ti816x
 type   : test type - func,stress, modular
          if the test is modular -ko option is required
 ko     : ko file if -test is modular
 h      : Displays the help/usage

4)Incase test suite uses LFTB executable, it will be present in <xxx_test_suite>/bin/<platform> directory. User can switch this directory to execute the single testcases by running the executable. Refer to executable by executing with -help option.
	
Point of contact
================
Please submit your queries or comments at the forums http://community.ti.com or http://support.ti.com
