1. 27 Jan, 2016 1 commit
    • Michael Schanz's avatar
      CGT000029 QMX6: remove revision check of EXT CSD · dad62bf8
      Michael Schanz authored
      Revision checking of EXT CSD area avoids that new eMMC devices are recognized
      at all. In the past, it has been observed that new types are still backward
      compatible and handled correctly, although not supported with complete feature set.
      This patch removes the revision checking of the EXT CSD area in order to get
      the driver working for devices with EXT_CSD rev. 6 and above.
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      dad62bf8
  2. 30 Nov, 2015 1 commit
  3. 20 Nov, 2015 1 commit
  4. 28 Oct, 2015 1 commit
    • Michael Schanz's avatar
      CGT000026 QMX6: adjust camera rst signal/Q7 GPIO1 for conga-QMX6 hardware revision C.x · 1c3ff9a2
      Michael Schanz authored
      In Q7 Spec. 2.0, the USB_OTG_PWR signal was moved from Q7 Connector, Pin 186 to Pin 56.
      Moreover the connector layout of the MIPI connector was specified.
      
      conga-QMX6 rev. C.x was designed according the new Q7 Spec. 2.0 (& Errata). In order to
      fulfill this requirement, this patch was released to adjust the device tree configuration.
      
      In detail, this patch
      - remaps the camera reset signal from GPIO1_8 (R5) to GPIO6_5 (L6). This frees GPIO1_8
      in order to be used as Q7 GPIO1 (Pin 186).
      
      - removes signal GPIO3_22 from the device tree configuration. In previous hardware
      revisions (e.g. A.x, B.x), this signal was used as Q7 GPIO1 (Pin 186).
      
      Attention: this patch breaks compatibility with rev. B.x boards when Q7 GPIO1 is in use.
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      1c3ff9a2
  5. 08 Oct, 2015 2 commits
  6. 19 Feb, 2015 5 commits
  7. 09 Feb, 2015 1 commit
  8. 16 Jan, 2015 1 commit
  9. 12 Dec, 2014 1 commit
  10. 20 Nov, 2014 9 commits
    • Michael Schanz's avatar
      CGT000009 QMX6: support for UART3 and UART5 · c5c5cfaf
      Michael Schanz authored
      add support for UART3 and UART5 in conga-QMX6 device tree configuration
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      c5c5cfaf
    • Michael Schanz's avatar
      CGT000008 QMX6: support for pwm beeper · 17e0a98b
      Michael Schanz authored
      add support for pwm beeper in conga-QMX6 devicetree configuration
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      17e0a98b
    • Michael Schanz's avatar
      CGT000007 QMX6: enable CAN interface · 9b64a9be
      Michael Schanz authored
      enable CAN interface in conga-QMX6 devicetree configuration
      
      The patch enables the first CAN bus channel in the conga-QMX6 devicetree configuration. In order
      to enable the second CAN bus channel as well, the status of the flexcan2 interface has to be set
      to "okay" in the device tree configuration, i.e. by specifying
      
      &flexcan2 {
      	status = "okay";
      };
      
      in the files /arch/arm/boot/dts/imx6q-qmx6.dts and /arch/arm/boot/dts/imx6dl-qmx6.dts
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      9b64a9be
    • Michael Schanz's avatar
      CGT000006 QMX6: optimize framebuffer configuration · fd9c0557
      Michael Schanz authored
      Optimize the framebuffer configuration in device tree setup in order to fix display setup
      for QC and DCL modules.
      
      This patch leads to a more general framebuffer configuration of the different QMX6 framebuffers.
      The default framebuffer configuration can be overwritten by a specific configuration given on
      the kernel command line for the primary display (fb0) and the secondary display (fb1), as usual,
      via video=mxcfb0:dev=... and video=mxcfb1:dev=... entries.
      
      The proper framebuffer configuration has been verified with the following command line setup:
      
      vmalloc=400 video=mxfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:ldb,LDB-SGA,if=RGB666 fbmem=28,10
      vmalloc=400 video=mxfb0:dev=ldb,LDB-SGA,if=RGB666 video=mxcfb1:hdmi,1920x1080M@60,if=RGB24 fbmem=10,28
      
      Observe that the framebuffer enumeration may change during boot time (e.g. mxcfb1 most likely does not
      correspond with /dev/fb1 but with /dev/fb2) because of the insertion of overlay devices.
      
      The default operating mode for the LVDS display bridge (LDB) is set to "sin0".
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      fd9c0557
    • Michael Schanz's avatar
      CGT000005 QMX6: add LVDS SGA (800x600) video mode · 75ef7b5b
      Michael Schanz authored
      Add LVDS SGA (800x600) video mode
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      75ef7b5b
    • Michael Schanz's avatar
      CGT000004 QMX6: fix wrong polarity of CD signal (usdhc2) · cbe6b6e3
      Michael Schanz authored
      Fix wrong signal polarity of card detect signal (usdhc2)
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      cbe6b6e3
    • Michael Schanz's avatar
      CGT000003 QMX6: improve QMX6 reset/reboot behaviour · 60352b24
      Michael Schanz authored
      Improves the QMX6 reset and reboot behaviour for low CPU frequency condition (at 396MHz)
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      60352b24
    • Michael Schanz's avatar
      CGT000002 QMX6: OV5640 MIPI camera support · 52c3ab30
      Michael Schanz authored
      Adds support for OV5640 MIPI camera
      
      Beside this patch the following additional changes to the hardware and to the bootloader
      software are required in order to get a correct working OV5640 MIPI camera on the conga-QMX6:
      
      1. hardware requirements/modifications:
      - the conga-QMX6 board (HW-Rev. B.x) needs a hardware patch in order to provide the correct
        supply voltage for the camera module (3.3V) at X9, Pins 29 and 30. This patch can be omitted,
        when the camera is connected through a conga-MCB mini carrier board.
      
      - when using the camera module (ACA1) to connect to the camera, ensure to use at least hardware
        revision X.1 of the camera module in order to provide 2.5V compliant signals to the OV5640 camera.
      
      2. software modifications:
      - the interface level of the camera interface has to be set to 2.5V.
        With QMX6 bootloader version 2013.04 (cgt_imx_v2013.04_3.10.17_1.0.0) this can be
        achieved by setting the environment variable "lv_mipi" to the value "2V5".
      
      Please contact your dedicated congatec support channel in order to get more detailed information
      about the camera interface and the related requirements and modifications to the hardware.
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      52c3ab30
    • Michael Schanz's avatar
      CGT000001 QMX6: Initial support · a3e22adb
      Michael Schanz authored
      Initial support for congatec conga-QMX6 Qseven i.MX6 ARM module
      Signed-off-by: Michael Schanz's avatarMichael Schanz <michael.schanz@congatec.com>
      a3e22adb
  11. 18 Sep, 2014 3 commits
  12. 20 Aug, 2014 2 commits
  13. 15 Aug, 2014 12 commits
    • Xianzhong's avatar
      ENGR00322632 [#1243] fix memory type to avoid overwriting issue · 77bb9f15
      Xianzhong authored
      fix invalid access issue in GPU kernel triggered with the certain condition,
      memory extensive type exceed 256 and will cause memory overwriting issue
      
      Date: Jul 14, 2014
      Signed-off-by: 's avatarXianzhong <b07117@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit 0db530ceadb9e1559793c725d4ab576370ffb1c2)
      77bb9f15
    • Xianzhong's avatar
      ENGR00325794 [#1087] fix video memory mutex sharing issue · 9ba72a16
      Xianzhong authored
      the root cause is video memory mutex is not global variable,
      it will cause video memory managment problem with mixed 2D/3D/VG.
      
      kernel panic with multiple instances stress test running glesx_viv.sh.
      
      Date: Jul 31, 2014
      Signed-off-by: 's avatarXianzhong <b07117@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit 02bdc91149f077aba37c790aca1e59041d473f71)
      (cherry picked from commit 26c25e084b4137bf19aaa20e5075bb3c16096066)
      (cherry picked from commit 94c683128e5b7b2d2aaa92de28a32500926b0fad)
      9ba72a16
    • Loren Huang's avatar
      ENGR00316978 [#1162] force_sig crash in GPU lower memory killer · d40445b3
      Loren Huang authored
      it is caused when multiple threads try to kill same one process,
      the global semaphore is used to avoid this conflict.
      
      Date: Jun 05, 2014
      Signed-off-by: 's avatarXianzhong <b07117@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit 48c860eba3aae80c85587a37a858082b3a8b7b08)
      (cherry picked from commit d6acc3d27428be0d0b4682ab86b76de03c54efab)
      d40445b3
    • Loren Huang's avatar
      ENGR00315583 [#1209] fix random data corruption in GPU memory · 79d49d73
      Loren Huang authored
      GPU memory node should not be used after node structure is destoryed,
      that will cause random GPU memory data corruption issue in Android platform.
      
      the issue can be reproduced when run cts -p android.opengl repeatly(more than 100 times)
      
      Date: May 28, 2014
      Signed-off-by: 's avatarXianzhong <b07117@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit 36dbe12f0dbd01dd7ef10b52a9c508fa5d7d19d0)
      (cherry picked from commit c81d392b824699088f88d4552cb1935d94d89dc3)
      79d49d73
    • Loren Huang's avatar
      ENGR00313862 [#1173] fix android cts testThroughput fail · a5de4eb9
      Loren Huang authored
      fix android.media.cts.PresentationSyncTest#testThroughput cts fail,
      root cause is dequeueBuffer and queueBuffer in Surface will acquire
      the same mutex and in GPU driver dequeueBuffer and queueBuffer is work
      at asynchronous mode, so queueBuffer maybe blocked by dequeueBuffer
      and dequeueBuffer will return after 16ms (vsync time).
      
      Date: May 16, 2014
      Signed-off-by: 's avatarRichard Liu <r66033@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit e62993b346e418f08cb88d25303a0541653a5468)
      (cherry picked from commit cb850fe07a406ecd4610b985b23b55b37dcdb703)
      a5de4eb9
    • Xianzhong's avatar
      ENGR00314119 [#1183] fixed database mutex multi-lock issue · 9d9d9235
      Xianzhong authored
      The abnormal flow with the monkey test freeze problem is as below:
      gckKERNEL_DestroyProcessDB--> aquire mutex --> gckCOMMAND_Detach(gckEVENT_FreeContiguousMemory) -->
      ___RemoveRecordFromProcessDB --> gckKERNEL_RemoveProcessDB --> aquire the same mutex
      
      the fix is to disable mutex lock when perform record destory operations
      
      Date: May 19, 2014
      Signed-off-by: 's avatarXianzhong <b07117@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit 8d62ea9a655f1bb0ca86af222de7625abc8d2bc8)
      (cherry picked from commit cd5a9a37525d4d2f79b6013f4bd93779b900b854)
      (cherry picked from commit 31d6a06da4cf9beacd9b1ba7a7e67d41cee18f7d)
      9d9d9235
    • Xianzhong's avatar
      ENGR00312477 [#1162] fixed gpu lower memory killer · 2c33e32d
      Xianzhong authored
      mutex operation is performed in gckKERNEL_QueryProcessDB
      remove spinlock for gckKERNEL_QueryProcessDB to avoid scheduling issue
      
      Date: May 08, 2014
      Signed-off-by: 's avatarXianzhong <b07117@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit 554581201c0a1c2c7caddad5750b1fd678e09c8c)
      (cherry picked from commit 78ecaf1c6475ee188a6a2a1dfbe954e457a28997)
      (cherry picked from commit 6837de20c0ce171bc16c7d779d6ac177b53d5529)
      2c33e32d
    • Xianzhong's avatar
      ENGR00308899 [#1087] enhanced GPU database protection · 6648f5e3
      Xianzhong authored
      the potential risk is found in special case when application exit,
      deleting record will cause the unexpected issue when process database is destoryed without atom protection
      
      the enhanced database patch should be applied to avoid the unexpected kernel issue
      
      Date: Apr 17, 2014
      Signed-off-by: 's avatarXianzhong <b07117@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit e799c1ae023264c0e1e1e41d448e30e2304944e1)
      (cherry picked from commit 7eb5273b6dd61d61c2ffe778bdb6d5032bbc1aa0)
      (cherry picked from commit ae4ba121bb72164183d7a47eb8a7c3ea316f6204)
      6648f5e3
    • Xianzhong's avatar
      ENGR00309915 [#1087] enhanced video memory mutex · 1b41d9cc
      Xianzhong authored
      this patch can fix NULL pointer issue in GPU kernel driver with the following log
      
      [<7f240438>] (gckEVENT_AddList+0x0/0x810 [galcore]) from [<7f239ebc>] (gckCOMMAND_Commit+0xf28/0x118c [galcore])
      [<7f238f94>] (gckCOMMAND_Commit+0x0/0x118c [galcore]) from [<7f2362dc>] (gckKERNEL_Dispatch+0x120c/0x24e4 [galcore])
      [<7f2350d0>] (gckKERNEL_Dispatch+0x0/0x24e4 [galcore]) from [<7f222280>] (drv_ioctl+0x390/0x540 [galcore])
      [<7f221ef0>] (drv_ioctl+0x0/0x540 [galcore]) from [<800facd0>] (vfs_ioctl+0x30/0x44)
      
      The false code is at 0x217bc where the 0-pointer happens (r3 = 0)
      
      gcuVIDMEM_NODE_PTR node = (gcuVIDMEM_NODE_PTR)(gcmUINT64_TO_PTR(Record->info.u.FreeVideoMemory.node));
         217b8:                e5953028             ldr           r3, [r5, #40]         ; 0x28
      
                      if (node->VidMem.memory->object.type == gcvOBJ_VIDMEM)
         217bc:                e5932000             ldr           r2, [r3]
         217c0:                e5922000             ldr           r2, [r2]
         217c4:                e152000a             cmp       r2, sl
                      {
                           gcmkVERIFY_OK(gckKERNEL_RemoveProcessDB(Event->kernel,
      
      Date: Apr 23, 2014
      Signed-off-by: 's avatarXianzhong <b07117@freescale.com>
      Acked-by: Jason Liu
      (cherry picked from commit fcde214d8c793d4dd785e47175b5833f1f3f5f1f)
      (cherry picked from commit 952142648d76fce2663ef649d9f988f1b7809815)
      (cherry picked from commit 9d7b33678f1f944f75644e958c3ceeb7f2e4bac9)
      1b41d9cc
    • Richard Liu's avatar
      ENGR00310166 [#1157] disable GPU recovery function · ee7c962b
      Richard Liu authored
      Disable GPU auto recovery so that GPU can dump the stack.
      GPU support auto recovery function, when GPU meet some issue
      it will try to do recovery, but most of cases GPU can't really
      recovery, we do find some cases GPU can recovery for example
      some 2D hang, but customer is not accept such recovery, so show
      the GPU stack dump and find the root cause is the correct way.
      
      Date: Apr 24, 2014
      Signed-off-by: 's avatarRichard Liu <r66033@freescale.com>
      (cherry picked from commit 888c79ab0f114b7b259266fc82c1399cbb926faf)
      (cherry picked from commit 8a213f47050eb49da70877090e07323b530bf147)
      (cherry picked from commit 6f779e52e7678aaab198ea4caa9bac1e686a44eb)
      ee7c962b
    • Loren Huang's avatar
      ENGR00308233-4 [#791]Refine wclip workaround algorithm 003 · 2e72d52d
      Loren Huang authored
      Vivante patch name:000e-more-refinements-for-wclip-issue
      
      Date: Apr 14, 2014
      Signed-off-by: 's avatarLoren Huang <b02279@freescale.com>
      Acked-by: Shawn Guo
      (cherry picked from commit 3fae441a3b6a40e4981473bf967c121e22a9eda7)
      (cherry picked from commit 46dcad78113f8c4757d8bb36a91f865ac6bc5afb)
      2e72d52d
    • Loren Huang's avatar
      ENGR00308233-3 [#791]Refine wclip workaround algorithm 002 · cc956fda
      Loren Huang authored
      Vivante patch name:0002-more-refinements-for-wclip-issue
      
      Date: Apr 14, 2014
      Signed-off-by: 's avatarLoren Huang <b02279@freescale.com>
      Acked-by: Shawn Guo
      (cherry picked from commit e25208c14fcfae452ebd378e33c671a8366ee55a)
      (cherry picked from commit c7d1eab0815f6034b78263e7c994179e3b897d1c)
      cc956fda