1. 04 Apr, 2013 15 commits
    • Archit Taneja's avatar
      arm: dss-common: don't use reset_gpio from omap4_panda_dvi_device · 29cdecab
      Archit Taneja authored
      gpio reset info is passed to the tfp410 panel driver via the panel's platform
      data struct 'tfp410_platform_data'. The tfp driver doesn't use the reset_gpio
      field in the omap4_panda_dvi_device struct. Remove this field.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      29cdecab
    • Archit Taneja's avatar
      arm: omap boards: Remove unnecessary platform_enable/disable callbacks for VENC devices · fe5c5fba
      Archit Taneja authored
      The omap_dss_device's platform_enable/disable callbacks don't do anything for
      any of the boards. The platform calls from the VENC driver will also be removed
      in the future. Remove these calls from the board which have a VENC device.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Acked-by: default avatarIgor Grinberg <grinberg@compulab.co.il>
      fe5c5fba
    • Archit Taneja's avatar
      arm: omap: dss-common: use picodlp panel's gpio handling · e5e53322
      Archit Taneja authored
      The dss-common file currently requests gpios required by the picodlp DPI
      panel on the 4430sdp/blaze board. It also requests DISPLAY_SEL_GPIO and
      DLP_POWER_ON_GPIO gpios which are board specific gpios to switch between lcd2
      panel and picodlp, and setting intermediate power supplies for picodlp
      respectively. These gpios are toggled through platform_enable/disable functions
      called by the picodlp driver.
      
      Remove the gpio requests for the gpios which are already requested by the panel
      driver, and remove the platform callback functions and set the platform specific
      gpios in such a way that lcd2 panel is selected for the LCD2 overlay manager and
      the power supplies for picodlp are disabled.
      
      Note: We need to revisit this so that we can enable and switch to picodlp if
      that's the only panel driver available for the LCD2 overlay manager.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      e5e53322
    • Archit Taneja's avatar
      arm: omap: board-omap3pandora: use tpo panel's gpio handling · 2af2ac7a
      Archit Taneja authored
      The omap3pandora board file currently passes the reset gpio number to the
      tpo-td043mtea1 panel driver via the reset_gpio field in omap_dss_device.
      
      Platform related information should be passed via the panel driver's platform
      data struct.
      
      Add the reset gpio information to panel_tpo_td043_data so that it's passed to
      the panel driver.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      2af2ac7a
    • Archit Taneja's avatar
      arm: omap: board-zoom: use NEC panel's gpio handling · 20012c77
      Archit Taneja authored
      The zoom board file currently requests gpios required by the nec-nl8048hl11-01
      dpi panel, and provides dummy platform_enable/disable callbacks.
      
      gpio request and configuration have been moved to the nec-nl8048hl11-01 panel
      driver itself and shouldn't be done in the board files.
      
      Remove the gpio requests and the platform callbacks from the board file. Add the
      gpio information to panel_nec_nl8048_data so that it's passed to the panel
      driver.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      20012c77
    • Archit Taneja's avatar
      arm: omap: board-rx-51: use acx565akm panel's gpio handling · 3c803f40
      Archit Taneja authored
      The rx-51 board file currently requests gpios required by the acx565akm panel,
      and provides platform_enable/disable callbacks to configure them.
      
      These tasks have been moved to the acx565akm panel driver itself and shouldn't
      be done in the board files.
      
      Remove the gpio requests and the platform callbacks from the board file. Pass
      the panel_acx565akm_data instance 'lcd_data' to omap_dss_device instead of
      passing the gpio number in omap_dss_device's reset_gpio.
      
      Add the gpio information to panel_acx565akm_data so that it's passed to the
      panel driver.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      3c803f40
    • Archit Taneja's avatar
      arm: omap: board-sdp3430: use sharp panel's gpio handling · a05f92b7
      Archit Taneja authored
      The omap3430sdp board file currently requests gpios required by the sharp_ls dpi
      panel, and provides platform_enable/disable callbacks to configure them.
      
      These tasks have been moved to the sharp_ls panel driver itself and shouldn't
      be done in the board files.
      
      Remove the gpio requests and the platform callbacks from the board file.
      Add the gpio information to panel_sharp_ls037v7dw01_data so that it's
      passed to the panel driver.
      
      Out of sharp panel's configurable pins, all apart from resb_gpio are managed by
      a CPLD on the display and set to a default value. Only the configurable pin is
      passed to platform data.
      
      The backlight GPIO doesn't go directly to the sharp panel, it is used to set up
      a voltage supply which goes to the LED+ pin of the panel, hence it isn't passed
      to panel as platform data, and configured in the board file itself. The
      backlight used to previously toggle through the platform_enable/disable
      callbacks, but now it is always on. This needs to be revisited.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      a05f92b7
    • Archit Taneja's avatar
      arm: omap: board-omap3evm: use sharp panel's gpio handling · fde38254
      Archit Taneja authored
      The omap3evm board file currently requests gpios required by the sharp_ls dpi
      panel, and provides platform_enable/disable callbacks to configure them.
      
      These tasks have been moved to the sharp_ls panel driver itself and shouldn't
      be done in the board files.
      
      Remove the gpio requests and the platform callbacks from the board file.
      Add the gpio information to panel_sharp_ls037v7dw01_data so that it's passed
      to the panel driver.
      
      Note: The GPIOs OMAP3EVM_LCD_PANEL_ENVDD and OMAP3EVM_LCD_PANEL_BKLIGHT_GPIO
      aren't directly connected to the sharp panel, hence they aren't passed to the
      panel driver as platform data. These are set to a default value such that LCD
      is enabled and backlight is on. These used to previously toggle through the
      platform_enable/disable callbacks, but now these are always on. This needs to
      be revisited.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      fde38254
    • Archit Taneja's avatar
      arm: omap: board-overo: use lb035q02 dpi panel's gpio handling · 5c4e5995
      Archit Taneja authored
      The overo board file currently requests gpios required by the lb035q02 panel,
      and provides platform_enable/disable callbacks to configure them.
      
      These tasks have been moved to the lb035q02 dpi panel driver itself and should
      be removed from the board files.
      
      The lb035q02 panel driver uses generic dpi panel's platform data struct
      internally. Remove the gpio requests and the platform callbacks from the board
      file. Add the gpio information to the generic dpi panel platform data struct so
      that it's passed to the panel driver.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      5c4e5995
    • Archit Taneja's avatar
      arm: omap: board-ldp: use generic dpi panel's gpio handling · fa2a02f2
      Archit Taneja authored
      The ldp board file currently requests gpios required to configure the NEC DPI
      panel, and provides platform_enable/disable callbacks to configure them.
      
      These tasks have been moved to the generic dpi panel driver itself and shouldn't
      be done in the board files.
      
      Remove the gpio requests and the platform callbacks from the board file.
      Configure the gpio information in generic dpi panel's platform data so that it's
      passed to the panel driver.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      fa2a02f2
    • Archit Taneja's avatar
      arm: omap: board-am3517: use generic dpi panel's gpio handling · 130cbe57
      Archit Taneja authored
      The am3517 board file currently requests gpios required to configure the sharp
      lq DPI panel, and provides platform_enable/disable callbacks to configure them.
      
      These tasks have been moved to the generic dpi panel driver itself and shouldn't
      be done in the board files.
      
      Remove the gpio requests and the platform callbacks from the board file.
      Add the gpio information to generic dpi panel's platform data so that it's
      passed to the panel driver.
      
      Note: It's not clear why the GPIOs were muxed as input signals in PULL down mode
      in am3517_evm_display_init(). Also, only the LCD_PANEL_PWR was toggled in the
      platform_enable/disable calls, the generic DPI panel driver will now toggle all
      the three gpios on panel's disable/enable. We need to test if these changes to
      see if they have any impact or not.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Vaibhav Hiremath <hvaibhav@ti.com>
      130cbe57
    • Tomi Valkeinen's avatar
      arm: omap: board-cm-t35: use generic dpi panel's gpio handling · e471e9ad
      Tomi Valkeinen authored
      The cm-t35 board file currently requests gpios required to configure the tdo35s
      panel, and provides platform_enable/disable callbacks to configure them.
      
      These tasks have been moved to the generic dpi panel driver itself and shouldn't
      be done in the board files.
      
      Remove the gpio requests and the platform callbacks from the board file.
      Add the gpio information to generic dpi panel's platform data so that it's
      passed to the panel driver.
      
      Note: Only BL enable gpio is handled in the panel driver. The LCD enable
      GPIO is handled in the board file at init time, as there's a 50 ms delay
      required when using the GPIO, and the panel driver doesn't know about
      that.
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Acked-by: default avatarIgor Grinberg <grinberg@compulab.co.il>
      e471e9ad
    • Archit Taneja's avatar
      arm: omap: board-devkit8000: use generic dpi panel's gpio handling · 9272d8bd
      Archit Taneja authored
      The devkit8000 board file currently requests gpios required to configure the
      innolux DPI panel, and provides platform_enable/disable callbacks to configure
      them.
      
      These tasks have been moved to the generic dpi panel driver itself and should
      be removed from the board files.
      
      Remove the gpio request and the platform callbacks from the board file.
      Configure the gpio information in generic dpi panel's platform data so that it's
      passed to the panel driver.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      9272d8bd
    • Archit Taneja's avatar
      arm: omap: board-2430: use generic dpi panel's gpio handling · 3b4ece75
      Archit Taneja authored
      The 2430sdp board file currently requests gpios required to configure the NEC
      DPI panel, and provides platform_enable/disable callbacks to configure them.
      
      These tasks have been moved to the generic dpi panel driver itself and shouldn't
      be done in the board files.
      
      Remove the gpio requests and the platform callbacks from the board file.
      Add the gpio information to generic dpi panel's platform data so that it's
      passed to the panel driver.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      3b4ece75
    • Peter Ujfalusi's avatar
      ARM: OMAP: zoom: Use pwm stack for lcd and keyboard backlight · c1c88137
      Peter Ujfalusi authored
      Use pwm_leds driver for the keyboard light and pwm-backlight for the lcd
      backlight control (instead of implementing the PWM driver part in the board
      file).
      Signed-off-by: default avatarPeter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      c1c88137
  2. 03 Apr, 2013 2 commits
    • Tomi Valkeinen's avatar
      OMAPDSS: add fields to panels' platform data · c3f80cbc
      Tomi Valkeinen authored
      Forthcoming panel patches will change the panel drivers to use platform
      data to pass panel's gpios to the panel driver. This patch adds the
      required fields and platform data structs to the omap-panel-data.h file,
      so that the board files can be changed independently of the panel driver
      changes.
      Signed-off-by: default avatarTomi Valkeinen <tomi.valkeinen@ti.com>
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      c3f80cbc
    • Archit Taneja's avatar
      OMAPDSS: panels: keep platform data of all panels in a single header · a0d8dde9
      Archit Taneja authored
      Structs for platform data of omapdss panels are found in headers in the
      'include/video/' path. Board files populate these structs with platform
      specific values, and the panel driver uses these to configure the panel.
      
      Currently, each panel has it's own header in the above path. Move all the
      omapdss panel platform data structs to a single header omap-panel-data.h.
      This is useful because:
      
      - All other omapdss panel drivers will be modified to use platform data. This
        would lead to a lot of panel headers usable only by omapdss. A lot of these
        platform data structs are trivial, and don't really need a separate header.
      - Platform data would be eventually removed, and platform information would be
        passed via device tree. Therefore, omapdss panel platform data structs are
        temporary, and will be easier to remove if they are all in the same header.
      - All board files will have to include the same header to configure a panel's
        platform data, that makes the board files more consistent.
      Signed-off-by: default avatarArchit Taneja <archit@ti.com>
      a0d8dde9
  3. 31 Mar, 2013 5 commits
    • Linus Torvalds's avatar
      Linux 3.9-rc5 · 07961ac7
      Linus Torvalds authored
      07961ac7
    • Linus Torvalds's avatar
      Merge branch 'fixes' of git://git.infradead.org/users/vkoul/slave-dma · 0bb44280
      Linus Torvalds authored
      Pull slave-dmaengine fixes from Vinod Koul:
       "Two fixes for slave-dmaengine.
      
        The first one is for making slave_id value correct for dw_dmac and
        the other one fixes the endieness in DT parsing"
      
      * 'fixes' of git://git.infradead.org/users/vkoul/slave-dma:
        dw_dmac: adjust slave_id accordingly to request line base
        dmaengine: dw_dma: fix endianess for DT xlate function
      0bb44280
    • Linus Torvalds's avatar
      Merge branch 'v4l_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media · a7b436d3
      Linus Torvalds authored
      Pull media fixes from Mauro Carvalho Chehab:
       "For a some fixes for Kernel 3.9:
         - subsystem build fix when VIDEO_DEV=y, VIDEO_V4L2=m and I2C=m
         - compilation fix for arm multiarch preventing IR_RX51 to be selected
         - regression fix at bttv crop logic
         - s5p-mfc/m5mols/exynos: a few fixes for cameras on exynos hardware"
      
      * 'v4l_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media:
        [media] [REGRESSION] bt8xx: Fix too large height in cropcap
        [media] fix compilation with both V4L2 and I2C as 'm'
        [media] m5mols: Fix bug in stream on handler
        [media] s5p-fimc: Do not attempt to disable not enabled media pipeline
        [media] s5p-mfc: Fix encoder control 15 issue
        [media] s5p-mfc: Fix frame skip bug
        [media] s5p-fimc: send valid m2m ctx to fimc_m2m_job_finish
        [media] exynos-gsc: send valid m2m ctx to gsc_m2m_job_finish
        [media] fimc-lite: Fix the variable type to avoid possible crash
        [media] fimc-lite: Initialize 'step' field in fimc_lite_ctrl structure
        [media] ir: IR_RX51 only works on OMAP2
      a7b436d3
    • Linus Torvalds's avatar
      Merge tag 'for-linus-20130331' of git://git.kernel.dk/linux-block · d299c290
      Linus Torvalds authored
      Pull block fixes from Jens Axboe:
       "Alright, this time from 10K up in the air.
      
        Collection of fixes that have been queued up since the merge window
        opened, hence postponed until later in the cycle.  The pull request
        contains:
      
         - A bunch of fixes for the xen blk front/back driver.
      
         - A round of fixes for the new IBM RamSan driver, fixing various
           nasty issues.
      
         - Fixes for multiple drives from Wei Yongjun, bad handling of return
           values and wrong pointer math.
      
         - A fix for loop properly killing partitions when being detached."
      
      * tag 'for-linus-20130331' of git://git.kernel.dk/linux-block: (25 commits)
        mg_disk: fix error return code in mg_probe()
        rsxx: remove unused variable
        rsxx: enable error return of rsxx_eeh_save_issued_dmas()
        block: removes dynamic allocation on stack
        Block: blk-flush: Fixed indent code style
        cciss: fix invalid use of sizeof in cciss_find_cfgtables()
        loop: cleanup partitions when detaching loop device
        loop: fix error return code in loop_add()
        mtip32xx: fix error return code in mtip_pci_probe()
        xen-blkfront: remove frame list from blk_shadow
        xen-blkfront: pre-allocate pages for requests
        xen-blkback: don't store dev_bus_addr
        xen-blkfront: switch from llist to list
        xen-blkback: fix foreach_grant_safe to handle empty lists
        xen-blkfront: replace kmalloc and then memcpy with kmemdup
        xen-blkback: fix dispatch_rw_block_io() error path
        rsxx: fix missing unlock on error return in rsxx_eeh_remap_dmas()
        Adding in EEH support to the IBM FlashSystem 70/80 device driver
        block: IBM RamSan 70/80 error message bug fix.
        block: IBM RamSan 70/80 branding changes.
        ...
      d299c290
    • Paul Walmsley's avatar
      Revert "lockdep: check that no locks held at freeze time" · dbf520a9
      Paul Walmsley authored
      This reverts commit 6aa97070.
      
      Commit 6aa97070 ("lockdep: check that no locks held at freeze time")
      causes problems with NFS root filesystems.  The failures were noticed on
      OMAP2 and 3 boards during kernel init:
      
        [ BUG: swapper/0/1 still has locks held! ]
        3.9.0-rc3-00344-ga937536b #1 Not tainted
        -------------------------------------
        1 lock held by swapper/0/1:
         #0:  (&type->s_umount_key#13/1){+.+.+.}, at: [<c011e84c>] sget+0x248/0x574
      
        stack backtrace:
          rpc_wait_bit_killable
          __wait_on_bit
          out_of_line_wait_on_bit
          __rpc_execute
          rpc_run_task
          rpc_call_sync
          nfs_proc_get_root
          nfs_get_root
          nfs_fs_mount_common
          nfs_try_mount
          nfs_fs_mount
          mount_fs
          vfs_kern_mount
          do_mount
          sys_mount
          do_mount_root
          mount_root
          prepare_namespace
          kernel_init_freeable
          kernel_init
      
      Although the rootfs mounts, the system is unstable.  Here's a transcript
      from a PM test:
      
        http://www.pwsan.com/omap/testlogs/test_v3.9-rc3/20130317194234/pm/37xxevm/37xxevm_log.txt
      
      Here's what the test log should look like:
      
        http://www.pwsan.com/omap/testlogs/test_v3.8/20130218214403/pm/37xxevm/37xxevm_log.txt
      
      Mailing list discussion is here:
      
        http://lkml.org/lkml/2013/3/4/221
      
      Deal with this for v3.9 by reverting the problem commit, until folks can
      figure out the right long-term course of action.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Mandeep Singh Baines <msb@chromium.org>
      Cc: Jeff Layton <jlayton@redhat.com>
      Cc: Shawn Guo <shawn.guo@linaro.org>
      Cc: <maciej.rutecki@gmail.com>
      Cc: Fengguang Wu <fengguang.wu@intel.com>
      Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Ben Chan <benchan@chromium.org>
      Cc: Oleg Nesterov <oleg@redhat.com>
      Cc: Tejun Heo <tj@kernel.org>
      Cc: Rafael J. Wysocki <rjw@sisk.pl>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      dbf520a9
  4. 30 Mar, 2013 1 commit
    • Linus Torvalds's avatar
      Merge git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending · 13d2080d
      Linus Torvalds authored
      Pull SCSI target fixes from Nicholas Bellinger:
       "This includes the bug-fix for a >= v3.8-rc1 regression specific to
        iscsi-target persistent reservation conflict handling (CC'ed to
        stable), and a tcm_vhost patch to drop VIRTIO_RING_F_EVENT_IDX usage
        so that in-flight qemu vhost-scsi-pci device code can detect the
        proper vhost feature bits.
      
        Also, there are two more tcm_vhost patches still being discussed by
        MST and Asias for v3.9 that will be required for the in-flight qemu
        vhost-scsi-pci device patch to function properly, and that should
        (hopefully) be the last target fixes for this round."
      
      * git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending:
        target: Fix RESERVATION_CONFLICT status regression for iscsi-target special case
        tcm_vhost: Avoid VIRTIO_RING_F_EVENT_IDX feature bit
      13d2080d
  5. 29 Mar, 2013 12 commits
  6. 28 Mar, 2013 5 commits