world leader in high performance signal processing
Trace:

Differences

This shows you the differences between two versions of the page.

linux-kernel:testing [2012/07/27 02:57]
vivili [Device driver test] add ADV7511
linux-kernel:testing [2013/04/18 05:46] (current)
sonicz [Others]
Line 123: Line 123:
 </code>The application selection is the same as that for ad1836 testing above. </code>The application selection is the same as that for ad1836 testing above.
   - **Audio driver test(AD1980)**   - **Audio driver test(AD1980)**
-    * Test the audio driver on BF548-EZKIT board.+    * Test the audio driver on BF548-EZKIT board. Obsolete now.
   - **Audio driver test(AD1981b)**   - **Audio driver test(AD1981b)**
-    * Test the audio card AD1981b. +    * Test the audio card AD1981b. Obsolete now
-  - **Audio driver test(ssm2602)** +  - **Audio driver test(ssm2603)** 
-    * Test the audio driver on BF527-EZKIT board. For detail please refer to:[[linux-kernel:drivers:ssm2602|ssm2602_setup]].+    * Test the audio driver on BF537-STAMP board. For detail please refer to:[[linux-kernel:drivers:ssm2602|ssm2602_setup]]
 +  - **Audio driver test(ad1938)** 
 +    * Test the audio driver on BF537-STAMP board. 
 +    * AOUT1 and AIN1 are used for audio output and input. Red RCA connector is right channel and white RCA connector is left channel. 
 +  - **Audio driver test(adau1761)** 
 +    * Test the audio driver adau1761 on BF609-EZKIT board. Connect Audio EI3 Extender Board to P1A port on BF609-EZKIT. 
 +    * On Audio EI3 Extender Board, J4 is Line-in and J2 is headphone.
   - **Audio multi-channel test**   - **Audio multi-channel test**
     * This is a 5.1 multi-channel test and bellow audio cards support it.      * This is a 5.1 multi-channel test and bellow audio cards support it. 
Line 164: Line 170:
   - **Video driver test - ADV7393**      - **Video driver test - ADV7393**   
     * For detailed information of ADV7393 video driver, please refer to the doc:[[linux-kernel:drivers:adv7393|ADV7393]].     * For detailed information of ADV7393 video driver, please refer to the doc:[[linux-kernel:drivers:adv7393|ADV7393]].
-    * For hardware introduction of ADV7393, please refer to :[[hw:cards:adv7393|ADV7393 Video Encoder Card]]. +    * In ADV7393 extender board, pin 2 & 3 of JP1 are connected. For more hardware introduction of ADV7393, please refer to :[[hw:cards:adv7393|ADV7393 Video Encoder Card]]
-  - **TFT LCD driver(LQ035,LQ043)**   +    * Test method: connect Composite output to TV Composite input, run video_test, a round bow tie pattern can be seen on TV with white background
 +  - **TFT LCD driver(LQ035,LQ043)**
     * Please look into the doc:[[hw:cards:tft-lcd]].     * Please look into the doc:[[hw:cards:tft-lcd]].
     * On BF527-EZKIT board version 2.2 with SHARP LQ035Q1DH02 TFT LCD, set sw26 [off on x x x x].     * On BF527-EZKIT board version 2.2 with SHARP LQ035Q1DH02 TFT LCD, set sw26 [off on x x x x].
 +    * BF526-EZBRD supports to add an adapter board Blackfin Landscape LCD EZ-Extender. Blackfin Landscape LCD EZ-Extender has a Sharp LQ035Q1DH02 3.5 inch LCD with resistive touch and a AD7879 Touch Screen Controller. Connect extender to BF526-EZBRD according to following rule: J1 to P3, J2 to P2. A detailed doc about how to config hardware setting is at [[hw:cards:landscape_lcd_ez-extender#hardware_configuration_bf526-ezbrd_rev_02|Hardware Configuration BF526-EZBRD ( Rev 0.2 )]]
   - **Serial driver test over UART port0(WT,WB)**   - **Serial driver test over UART port0(WT,WB)**
     *To see if the serial port can receive the string and command sequencially and exactly, which will be shown on the screen through kermit. If the strings printed and commands executed are as expected, the case passes, otherwise it fails.     *To see if the serial port can receive the string and command sequencially and exactly, which will be shown on the screen through kermit. If the strings printed and commands executed are as expected, the case passes, otherwise it fails.
Line 302: Line 310:
     * Support CF Memory card in true IDE mode to be read/written by STAMP board.     * Support CF Memory card in true IDE mode to be read/written by STAMP board.
     * Please refer to the page for details [[hw:cards:cf-ide-nand|the CF card doc]].     * Please refer to the page for details [[hw:cards:cf-ide-nand|the CF card doc]].
-  - **802.11 wireless card test** +  - **802.11 wireless CF card test** 
-    * Support wireless ethernet card on STAMP board, which can have connection with wireless AP and do communication. +    * Support wireless 802.11 CF card on BF537-STAMP board through a [[hw:cards:cf-ide-nand|CF/IDE-ATA/NAND BF537 STAMP EXTENDER]]. 
-    * Please refer to the page for details [[linux-kernel:drivers:bfin_cf_pcmcia|PCMCIA Introduction - Driver Example 802.11 CompactFlash Cards]].+    * Test method: connect to wireless AP and do communication with it. 
 +    * Hardware setting on BF537-STAMP: SW5 all OFF; SW6.4 OFF
 +    * Please refer to the page for details [[linux-kernel:drivers:bfin_cf_pcmcia#compactflash_cards|802.11 CompactFlash Cards]].
   - **802.11 wifi card through sdio**   - **802.11 wifi card through sdio**
     * Support wifi card on BF548-EZKIT and BF518F-EZBRD, which have sdio mmc port.     * Support wifi card on BF548-EZKIT and BF518F-EZBRD, which have sdio mmc port.
 +    * The SDIO WIFI card is not reset properly if you hit the reset button referring to bug 7493. Please re-plug power before test.
     * Please refer to the page for details [[linux-kernel:drivers:wifi_over_sdio|Wifi over SDIO]].     * Please refer to the page for details [[linux-kernel:drivers:wifi_over_sdio|Wifi over SDIO]].
   - **adf7021 - High Performance Narrowband ISM Transceiver**   - **adf7021 - High Performance Narrowband ISM Transceiver**
Line 328: Line 339:
   - **SPI MMC driver**   - **SPI MMC driver**
     * Test the MMC/SD SPI addon card driver.     * Test the MMC/SD SPI addon card driver.
-    * Details at: [[linux-kernel:drivers:spi_mmc|Blackfin MMC Driver]].  +    * Pay attention to Switch setting in spi mmc add-on card. Default CS is 4 so switch 5 is on. In current regression CS is changed from 4 to 1, so switch 2 is on. Details at: [[linux-kernel:drivers:spi_mmc|Blackfin MMC Driver]].  
-  - **Bluetooth**  +  - **Bluetooth (usb)**  
-    * To use bluetooth protocal on stamp board. Details at:[[linux-kernel:drivers:bluetooth_usb| bluetooth]].+    * To use bluetooth protocal on stamp board via usb port. Details at:[[linux-kernel:drivers:bluetooth_usb| Bluetooth on USB]]. 
 +    * Make sure bluetooth signal is strong enough during test, otherwise l2ping may fail. 
 +    * Make sure bluetooth service is OK after long time running on host machine and better not to use use usb hub. Please refer to buildroot bug [#7061].
   - **Bluetooth ALSA**    - **Bluetooth ALSA** 
     * To use bluetooth headphone with blackfin board.     * To use bluetooth headphone with blackfin board.
Line 339: Line 352:
   - **IRDA driver**   - **IRDA driver**
     * Communicate through IRDA to IRDA devices.     * Communicate through IRDA to IRDA devices.
-    * Modules of bfin_sir and irtty-sir are tested. To test irtty-sir, we should follow: <code>+    * Driver modules of bfin_sir and irtty-sir need to be tested
 +    * Driver bfin_sir is tested between two blackfin boards. We don't test it at present as we don't have enough good irda boards to test. 
 +    * Driver irtty-sir is tested between blackfin board and a linux PC with irda device. To test irtty-sir, we should use bellow serial port: <code>
 Board Type     Serial Port    irtty-sir Board Type     Serial Port    irtty-sir
 BF537-STAMP       UART0         UART1     BF537-STAMP       UART0         UART1    
Line 346: Line 361:
 BF527-EZKIT       UART1         UART0 BF527-EZKIT       UART1         UART0
 * only a UART0. Serial Port needs to be disabled before using irtty-sir on UART0.</code> * only a UART0. Serial Port needs to be disabled before using irtty-sir on UART0.</code>
-    * Test coverage in platform: Blackfin board to Blackfin board; Blackfin board to PC. +    * Test methods: Use irdaping to ping IRDA device; Use ircp to send/receive files.
-    * Test coverage in methods: Use irdaping to ping IRDA device; Use ircp to send/receive files.+
     * Details at:[[:irda_framework| irda_framework]].     * Details at:[[:irda_framework| irda_framework]].
   - **hardware flow controll RTS/CTS test**   - **hardware flow controll RTS/CTS test**
Line 407: Line 421:
     * Chip select for BF537-STAMP and BF527-EZKIT is CS1, interrupt is 4. There are some hardware settings required for BF527-EZKIT board(1.4): populate JP3 and disable SW11.2, SW18.1. Settings for BF527-EZKIT board(2.2): populate JP7 and disable SW11.2, enable SW28 to both on.     * Chip select for BF537-STAMP and BF527-EZKIT is CS1, interrupt is 4. There are some hardware settings required for BF527-EZKIT board(1.4): populate JP3 and disable SW11.2, SW18.1. Settings for BF527-EZKIT board(2.2): populate JP7 and disable SW11.2, enable SW28 to both on.
     * For BF609-EZKIT, CS7 and interrupt 6 on AD7877 board should be set. AD7877 board has poor connection between touchscreen and AD7877 board. PENIRQ will light when touch event has been received. The touchscreen extension is not directly connected to BF609-EZKIT, and a BF609 expansion adaptor board is needed. Detailed info is at [[hw:cards:609_adaptor|BF609 adaptor]].     * For BF609-EZKIT, CS7 and interrupt 6 on AD7877 board should be set. AD7877 board has poor connection between touchscreen and AD7877 board. PENIRQ will light when touch event has been received. The touchscreen extension is not directly connected to BF609-EZKIT, and a BF609 expansion adaptor board is needed. Detailed info is at [[hw:cards:609_adaptor|BF609 adaptor]].
 +    * BF526-EZBRD also supports touchscreen function with adapter board Blackfin Landscape LCD EZ-Extender. Blackfin Landscape LCD EZ-Extender has a Sharp LQ035Q1DH02 3.5 inch LCD with resistive touch and a AD7879 Touch Screen Controller. Connect extender to BF526-EZBRD according to following rule: J1 to P3, J2 to P2. A detailed doc about how to config hardware setting is at [[hw:cards:landscape_lcd_ez-extender#hardware_configuration_bf526-ezbrd_rev_02|Hardware Configuration BF526-EZBRD ( Rev 0.2 )]]
     * A detailed doc that can be referred to [[ad>software/driver/linux/ad7877/examples|touch_screen]]     * A detailed doc that can be referred to [[ad>software/driver/linux/ad7877/examples|touch_screen]]
   - **Power**   - **Power**
-    * Test power management. Make sure kernel can enter "Standby" or "Suspend-to-RAM" states, then it is waken up by rtc interrupt. +    * Test power management. Make sure kernel can enter "Standby" or "Suspend-to-RAM" states, then it is waken up by rtc interrupt in bf5xx board. In BF609-EZKIT, it is waken up by pushing button SW10
-    * This test should be done in several drivers: ethernet, ad1836, ad1981b, ad73311, ssm2602, adv7393 and tftlcd. +    * This test should be done in several drivers: ethernet, ad1836, ssm2603, adv7393 and tftlcd. 
-    * According to bug 5370, a pull down resistor is needed when Suspend-to-RAM. For 537-stamp/533-stamp/533-ezkit/527-ezkit/538-ezkit, add a 6.8k Ohm resistor between SCKE (J2-81) and GND (J2-87); and for 518f-ezbrd/526-ezbrd, add resistor between P5-B12 and P5-B13. 548-ezkit uses DDR SDRAM, and it's not affected by this bug.+    * According to bug 5370, a pull down resistor is needed when Suspend-to-RAM. For 537-stamp/533-stamp/533-ezkit/527-ezkit/538-ezkit, add a 6.8k Ohm resistor between SCKE (J2-81) and GND (J2-87); and for 518f-ezbrd/526-ezbrd, add resistor between P5-B12 and P5-B13. 548-ezkit uses DDR SDRAM, and it's not affected by this bug. BF609-EZKIT is also not affected by this bug.
     * Detail of power management is at :[[:power_management_support|Power Management Support]]     * Detail of power management is at :[[:power_management_support|Power Management Support]]
   - **Power test with usb gadget driver**   - **Power test with usb gadget driver**
     * After kernel wake up from "Standby" states, usb gadget driver should work. Test method is similar to above test "Power".     * After kernel wake up from "Standby" states, usb gadget driver should work. Test method is similar to above test "Power".
     * Test case is in folder power_usbdev. For detail of power management test, please refer to [[:power_management_support|Power Management Support]].     * Test case is in folder power_usbdev. For detail of power management test, please refer to [[:power_management_support|Power Management Support]].
-  - **Power management test over uart**+  - **Power management test over uart(uart_wakeup)**
     * Test power management with power saving mode of sleep. Make sure kernel can enter "Standby" states, then wake up by uart interrupt. "mem" is not supported.     * Test power management with power saving mode of sleep. Make sure kernel can enter "Standby" states, then wake up by uart interrupt. "mem" is not supported.
     * For detail of power management test, please refer to [[:power_management_support|Power Management Support]].     * For detail of power management test, please refer to [[:power_management_support|Power Management Support]].
-  - **Power management test over ethernet**+  - **Power management test over ethernet(ethernet_wakeup)**
     * Test power management with power saving mode of sleep. Make sure kernel can enter "Standby" states, then wake up by ethernet interrupt. "mem" is not supported.     * Test power management with power saving mode of sleep. Make sure kernel can enter "Standby" states, then wake up by ethernet interrupt. "mem" is not supported.
     * For detail of power management test, please refer to [[:power_management_support|Power Management Support]].     * For detail of power management test, please refer to [[:power_management_support|Power Management Support]].
-  - **V4L2 Video Capture Driver** +  - **Power management test over usb(usb_wakeup)** 
-    * VS6624: connect STAMP_PPI port in the CMOS Camera card(VS6624) to PPI port in BF537-STAMP. Hardware of CMOS Camera card is at [[hw:cards:cmos_camera|CMOS Camera Add-On-Card]] +    * Test power management with power saving mode of sleep. Make sure kernel can enter "mem" states, then wake up by usb interrupt. "Standby" is not supported. 
-    * ADV7842: connect ADV7842 adapter board to BF609-EZKIT P1A connector.+    * For detail of power management test, please refer to [[:power_management_support|Power Management Support]]. 
 +  - **V4L2 Video Capture Driver - Camera** 
 +    * VS6624: connect STAMP_PPI port in the CMOS Camera card(VS6624) to PPI port in BF537-STAMP. For BF609-EZKIT, it needs an adapter board from P1A slot to PPI port. Hardware of CMOS Camera card is at [[hw:cards:cmos_camera|CMOS Camera Add-On-Card]] 
 +    * ADV7842: connect ADV7842 adapter board directly to BF609-EZKIT P1A connector. Bellow formats need to be tested: 720p60(HD), NTSC and PAL. When test 720p60, connect HDMI wire from source to HDMIA port. When test NTSC and PAL, connect source to composite port. For details please refer to [[linux-kernel:drivers:v4l2_blackfin_capture#adv7842_example|ADV7842 Example]] 
 +    * Aptina MT9M114: connect Aptina MT9M114 board(P9 connector) to BF609-EZKIT P1A connector via Aptina camera adapter board(J2 connector).
     * For details please refer to [[linux-kernel:drivers:v4l2_blackfin_capture|Blackfin v4l Video Capture Driver]]     * For details please refer to [[linux-kernel:drivers:v4l2_blackfin_capture|Blackfin v4l Video Capture Driver]]
   - **ADV7183 video decoder**   - **ADV7183 video decoder**
Line 432: Line 451:
     * For details please refer to [[linux-kernel:drivers:v4l2_blackfin_capture#adv7183_example|adv7183 example]]     * For details please refer to [[linux-kernel:drivers:v4l2_blackfin_capture#adv7183_example|adv7183 example]]
   - **V4L2 Video Display Driver**   - **V4L2 Video Display Driver**
-    * ADV7511: connect ADV7511 adapter board to BF609-EZKIT P3A connector.+    * ADV7511: connect ADV7511 adapter board to BF609-EZKIT P3A connector. Only HD format is support for ADV7511, so connect HDMI wire card to TV to display captured HD yuv file (720p).
     * For details please refer to [[linux-kernel:drivers:v4l2_blackfin_display|Blackfin v4l2 Video Display Driver]]     * For details please refer to [[linux-kernel:drivers:v4l2_blackfin_display|Blackfin v4l2 Video Display Driver]]
   - **MPU**   - **MPU**
Line 957: Line 976:
  
  
-===== Limitations ===== +===== Limitations =====  
-The kernel testing at various system clock and core clock is not carried out at the moment.+The kernel testing at various system clock and core clock is not carried out at the moment.  
 + 
 +===== Others ===== 
 +  * [[PC_ubuntu_setup| How to set up ubuntu 12.04 on regression PC]] 
 +  * [[manual_test| Steps to run manual test suites]]