13 Dec, 2011

1 commit


30 Nov, 2011

1 commit


29 Nov, 2011

2 commits


28 Nov, 2011

1 commit


23 Nov, 2011

1 commit

  • This patch is added to route CPSW interrupts through ICSS module.
    CPSW CPSW_RX and CPSW_TX interrupts are not directly used from CPSW
    and instead they are routed through Timer module. This is done as an
    software workaround for enabling interrupt pacing feature. As interrupt
    Pacing works on C0_RX_PULSE interrupt connection to A8 INTC, which is
    not connected to Cortex A8 interrupt controller directly due to hw issue,
    it prevents interrupt pacing to work in AM33xx EVM. Therefore, Timer
    capture module is used to pickup these interrupts and routed to A8 INTC.

    Signed-off-by: Chandan Nath
    Signed-off-by: Afzal Mohammed

    Afzal Mohammed
     

22 Nov, 2011

1 commit


21 Nov, 2011

1 commit

  • This patch cleans-up the driver based on internal lpr comments.
    Separated board specific and SOC specific data and added to
    appropriate files. Based on the EVM type it will initialize the
    DCAN instance

    This patch cleans-up the driver according to Alpha EVM board
    changes. Modified pinmux settings added udelay(1); for raminit.
    Without this delay interrupts of the DCAN module is cleared while
    first time CAN network-up.

    Signed-off-by: Anil Kumar Ch

    Anil Kumar Ch
     

14 Nov, 2011

1 commit


27 Oct, 2011

10 commits


05 Oct, 2011

2 commits


16 Sep, 2011

1 commit

  • All of the device init and device driver interaction with omap_device
    is done using platform_device pointers. To make this more explicit,
    have omap_device return a platform_device pointer instead of an
    omap_device pointer.

    All current users of the omap_device pointer were only using it to get
    at the platform_device pointer or struct device pointer, so fixing all
    of the users was trivial.

    This also makes it more difficult for device init code to directly
    access members of struct omap_device, and allows for easier changing
    of omap_device internals.

    Cc: Paul Walmsley
    Signed-off-by: Kevin Hilman

    Kevin Hilman
     

05 Jul, 2011

1 commit


01 Jun, 2011

1 commit


31 Mar, 2011

1 commit


28 Mar, 2011

1 commit


25 Mar, 2011

1 commit

  • * 'v4l_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6: (442 commits)
    [media] videobuf2-dma-contig: make cookie() return a pointer to dma_addr_t
    [media] sh_mobile_ceu_camera: Do not call vb2's mem_ops directly
    [media] V4L: soc-camera: explicitly require V4L2_BUF_TYPE_VIDEO_CAPTURE
    [media] v4l: soc-camera: Store negotiated buffer settings
    [media] rc: interim support for 32-bit NEC-ish scancodes
    [media] mceusb: topseed 0x0011 needs gen3 init for tx to work
    [media] lirc_zilog: error out if buffer read bytes != chunk size
    [media] lirc: silence some compile warnings
    [media] hdpvr: use same polling interval as other OS
    [media] ir-kbd-i2c: pass device code w/key in hauppauge case
    [media] rc/keymaps: Remove the obsolete rc-rc5-tv keymap
    [media] remove the old RC_MAP_HAUPPAUGE_NEW RC map
    [media] rc/keymaps: Rename Hauppauge table as rc-hauppauge
    [media] rc-rc5-hauppauge-new: Fix Hauppauge Grey mapping
    [media] rc-rc5-hauppauge-new: Add support for the old Black RC
    [media] rc-rc5-hauppauge-new: Add the old control to the table
    [media] rc-winfast: Fix the keycode tables
    [media] a800: Fix a few wrong IR key assignments
    [media] opera1: Use multimedia keys instead of an app-specific mapping
    [media] dw2102: Use multimedia keys instead of an app-specific mapping
    ...

    Fix up trivial conflicts (remove/modify and some real conflicts) in:
    arch/arm/mach-omap2/devices.c
    drivers/staging/Kconfig
    drivers/staging/Makefile
    drivers/staging/dabusb/dabusb.c
    drivers/staging/dabusb/dabusb.h
    drivers/staging/easycap/easycap_ioctl.c
    drivers/staging/usbvideo/usbvideo.c
    drivers/staging/usbvideo/vicam.c

    Linus Torvalds
     

22 Mar, 2011

4 commits


19 Mar, 2011

1 commit


09 Mar, 2011

2 commits


03 Mar, 2011

1 commit


02 Mar, 2011

3 commits

  • OMAP2420 platform consists of mmc block as in omap1 and not the
    hsmmc block as present in omap2430, omap3, omap4 platforms.
    Removing all base address macro defines except keeping one for OMAP2420 and
    adapting only hsmmc device registration and driver to hwmod framework.

    Changes involves:
    1) Remove controller reset in devices.c which is taken care of
    by hwmod framework.
    2) Using omap-device layer to register device and utilizing data from
    hwmod data file for base address, dma channel number, Irq_number,
    device attribute.
    3) Update the driver to use dev_attr to find whether controller
    supports dual volt cards

    Signed-off-by: Paul Walmsley
    Signed-off-by: Kishore Kadiyala
    Reviewed-by: Balaji T K
    Cc: Benoit Cousson
    CC: Kevin Hilman
    Cc: Tony Lindgren
    Signed-off-by: Tony Lindgren

    Kishore Kadiyala
     
  • Moving the definition of mux setting API from devices.c to hsmmc.c
    and renaming it from "omap2_mmc_mux" to "omap_hsmmc_mux".
    Also calling "omap_hsmmc_mux" from omap2_hsmmc_init.

    Signed-off-by: Kishore Kadiyala
    Cc: Chris Ball

    Kishore Kadiyala
     
  • The MMC controller on the OMAP2420 is different from those
    on the OMAP2430, OMAP3 and OMAP4 families - all of the latter
    are identical. The one on the OMAP2420 is closer to that
    on OMAP1 chips.

    Currently, the n8x0 is the only OMAP2420 platform supported
    in mainline which registers the MMC controller. Upcoming
    changes to register the controllers using hwmod data are
    potentially invasive. To reduce the risk, separate out the
    2420 controller registration from the common init function
    and update its only user. Also seperating out mux settings
    for OMAP2420.

    Signed-off-by: Anand Gadiyar
    Signed-off-by: Kishore Kadiyala
    Cc: Tony Lindgren
    Cc: Madhusudhan Chikkature
    Cc: Chris Ball
    Signed-off-by: Tony Lindgren

    Anand Gadiyar
     

25 Feb, 2011

1 commit

  • Remove static platform_device and resource data within
    omap mailbox driver; use the one defined in the hwmod
    database along with omap_device framework for device
    build and registration.

    Add device latency functions to be used, so clock can be
    enabled and sysconfig is configured.

    Signed-off-by: Felipe Contreras
    Signed-off-by: Omar Ramirez Luna
    Signed-off-by: Tony Lindgren

    Felipe Contreras
     

24 Feb, 2011

1 commit