1. 01 11月, 2011 2 次提交
  2. 21 10月, 2011 1 次提交
  3. 19 10月, 2011 1 次提交
  4. 03 10月, 2011 1 次提交
    • A
      OMAPDSS/OMAP_VOUT: Fix incorrect OMAP3-alpha compatibility setting · 11354dd5
      Archit Taneja 提交于
      On OMAP3, in order to enable alpha blending for LCD and TV managers, we needed
      to set LCDALPHABLENDERENABLE/TVALPHABLENDERENABLE bits in DISPC_CONFIG. On
      OMAP4, alpha blending is always enabled by default, if the above bits are set,
      we switch to an OMAP3 compatibility mode where the zorder values in the pipeline
      attribute registers are ignored and a fixed priority is configured.
      
      Rename the manager_info member "alpha_enabled" to "partial_alpha_enabled" for
      more clarity. Introduce two dss_features FEAT_ALPHA_FIXED_ZORDER and
      FEAT_ALPHA_FREE_ZORDER which represent OMAP3-alpha compatibility mode and OMAP4
      alpha mode respectively. Introduce an overlay cap for ZORDER. The DSS2 user is
      expected to check for the ZORDER cap, if an overlay doesn't have this cap, the
      user is expected to set the parameter partial_alpha_enabled. If the overlay has
      ZORDER cap, the DSS2 user can assume that alpha blending is already enabled.
      
      Don't support OMAP3 compatibility mode for now. Trying to read/write to
      alpha_blending_enabled sysfs attribute issues a warning for OMAP4 and does not
      set the LCDALPHABLENDERENABLE/TVALPHABLENDERENABLE bits.
      
      Change alpha_enabled to partial_alpha_enabled in the omap_vout driver. Use
      overlay cap "OMAP_DSS_OVL_CAP_GLOBAL_ALPHA" to check if overlay supports alpha
      blending or not. Replace this with checks for VIDEO1 pipeline.
      
      Cc: linux-media@vger.kernel.org
      Cc: Lajos Molnar <molnar@ti.com>
      Signed-off-by: NArchit Taneja <archit@ti.com>
      Acked-by: NVaibhav Hiremath <hvaibhav@ti.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      11354dd5
  5. 30 9月, 2011 1 次提交
    • T
      OMAPDSS: remove vaddr from overlay info · 212b0d50
      Tomi Valkeinen 提交于
      overlay_info struct, used to configure overlays, currently includes both
      physical and virtual addresses for the pixels. The vaddr was added to
      support more exotic configurations where CPU would be used to update a
      display, but it is not currently used and there has been no interest in
      the feature. Using CPU to update a screen is also less interesting now
      that OMAP4 has two LCD outputs.
      
      This patch removes the vaddr field, and modifies the users of omapdss
      accordingly. This makes the use of omapdss a bit simpler, as the user
      doesn't need to think if it needs to give the vaddr.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      212b0d50
  6. 28 9月, 2011 1 次提交
  7. 22 9月, 2011 6 次提交
  8. 15 9月, 2011 1 次提交
  9. 14 9月, 2011 1 次提交
    • J
      iommu/omap: Fix build error with !IOMMU_SUPPORT · 7b6d45f1
      Joerg Roedel 提交于
      Without this patch it is possible to select the VIDEO_OMAP3
      driver which then selects OMAP_IOVMM. But the omap iommu
      driver is not compiled without IOMMU_SUPPORT enabled. Fix
      that by forcing OMAP_IOMMU and OMAP_IOVMM are enabled before
      VIDEO_OMAP3 can be selected.
      
      Cc: Ohad Ben-Cohen <ohad@wizery.com>
      Cc: iommu@lists.linux-foundation.org
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: NJoerg Roedel <joerg.roedel@amd.com>
      7b6d45f1
  10. 11 9月, 2011 5 次提交
  11. 26 8月, 2011 3 次提交
  12. 25 8月, 2011 2 次提交
  13. 29 7月, 2011 2 次提交
    • S
      [media] ov5642: include module.h for its facilities · d208c97c
      Stephen Rothwell 提交于
      drivers/media/video/ov5642.c:985:1: warning: data definition has no type or storage class
      drivers/media/video/ov5642.c:985:1: warning: type defaults to 'int' in declaration of 'MODULE_DEVICE_TABLE'
      drivers/media/video/ov5642.c:985:1: warning: parameter names (without types) in function declaration
      drivers/media/video/ov5642.c: In function 'ov5642_mod_init':
      drivers/media/video/ov5642.c:998:9: error: 'THIS_MODULE' undeclared (first use in this function)
      drivers/media/video/ov5642.c:998:9: note: each undeclared identifier is reported only once for each function it appears in
      drivers/media/video/ov5642.c: At top level:
      drivers/media/video/ov5642.c:1009:20: error: expected declaration specifiers or '...' before string constant
      drivers/media/video/ov5642.c:1009:1: warning: data definition has no type or storage class
      drivers/media/video/ov5642.c:1009:1: warning: type defaults to 'int' in declaration of 'MODULE_DESCRIPTION'
      drivers/media/video/ov5642.c:1009:20: warning: function declaration isn't a prototype
      drivers/media/video/ov5642.c:1010:15: error: expected declaration specifiers or '...' before string constant
      drivers/media/video/ov5642.c:1010:1: warning: data definition has no type or storage class
      drivers/media/video/ov5642.c:1010:1: warning: type defaults to 'int' in declaration of 'MODULE_AUTHOR'
      drivers/media/video/ov5642.c:1010:15: warning: function declaration isn't a prototype
      drivers/media/video/ov5642.c:1011:16: error: expected declaration specifiers or '...' before string constant
      drivers/media/video/ov5642.c:1011:1: warning: data definition has no type or storage class
      drivers/media/video/ov5642.c:1011:1: warning: type defaults to 'int' in declaration of 'MODULE_LICENSE'
      drivers/media/video/ov5642.c:1011:16: warning: function declaration isn't a prototype
      drivers/media/video/ov5642.c: In function 'ov5642_mod_init':
      drivers/media/video/ov5642.c:999:1: warning: control reaches end of non-void function
      Signed-off-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      d208c97c
    • M
      [media] em28xx: Fix DVB-C maxsize for em2884 · f7acc4bb
      Mauro Carvalho Chehab 提交于
      The logic at em28xx_isoc_dvb_max_packetsize() sucks, at least for newer
      the needed packet size. Yet, it is better than nothing.
      
      Rewrite the code in order to change the default to 752 for em2884 and
      newer chips and provide a better way to handle per-chipset specifics.
      
      For em2874, the current default should be enough, as the only em2874
      board is currently a 1-seg ISDB-T board, so, it needs only a limited
      amount of bandwidth.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      f7acc4bb
  14. 28 7月, 2011 13 次提交