31 Jul, 2013

1 commit


09 Apr, 2013

5 commits


08 Apr, 2013

1 commit


12 Mar, 2013

1 commit


13 Feb, 2013

11 commits


15 Dec, 2012

1 commit

  • Instead of using cpu_is_omap..() macros in the device driver we
    rely on information provided in the platform data.

    The only information we need is whether the USB Host module has
    a single ULPI bypass control bit for all ports or individual bypass
    control bits for each port. OMAP3 REV2.1 and earlier have the former.

    Signed-off-by: Roger Quadros
    Acked-by: Samuel Ortiz
    [tony@atomide.com: updated to remove plat/cpu.h]
    Signed-off-by: Tony Lindgren

    Roger Quadros
     

13 Dec, 2012

1 commit

  • Pull ARM SoC Header cleanups from Olof Johansson:
    "This is a collection of header file cleanups, mostly for OMAP and
    AT91, that keeps moving the platforms in the direction of
    multiplatform by removing the need for mach-dependent header files
    used in drivers and other places."

    Fix up mostly trivial conflicts as per Olof.

    * tag 'headers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (106 commits)
    ARM: OMAP2+: Move iommu/iovmm headers to platform_data
    ARM: OMAP2+: Make some definitions local
    ARM: OMAP2+: Move iommu2 to drivers/iommu/omap-iommu2.c
    ARM: OMAP2+: Move plat/iovmm.h to include/linux/omap-iommu.h
    ARM: OMAP2+: Move iopgtable header to drivers/iommu/
    ARM: OMAP: Merge iommu2.h into iommu.h
    atmel: move ATMEL_MAX_UART to platform_data/atmel.h
    ARM: OMAP: Remove omap_init_consistent_dma_size()
    arm: at91: move at91rm9200 rtc header in drivers/rtc
    arm: at91: move reset controller header to arm/arm/mach-at91
    arm: at91: move pit define to the driver
    arm: at91: move at91_shdwc.h to arch/arm/mach-at91
    arm: at91: move board header to arch/arm/mach-at91
    arn: at91: move at91_tc.h to arch/arm/mach-at91
    arm: at91 move at91_aic.h to arch/arm/mach-at91
    arm: at91 move board.h to arch/arm/mach-at91
    arm: at91: move platfarm_data to include/linux/platform_data/atmel.h
    arm: at91: drop machine defconfig
    ARM: OMAP: Remove NEED_MACH_GPIO_H
    ARM: OMAP: Remove unnecessary mach and plat includes
    ...

    Linus Torvalds
     

29 Nov, 2012

2 commits

  • CONFIG_HOTPLUG is going away as an option so __devexit is no
    longer needed.

    Signed-off-by: Bill Pemberton
    Cc: Srinidhi Kasagar
    Cc: Peter Tyser
    Cc: Daniel Walker
    Cc: Bryan Huntsman
    Acked-by: David Brown
    Acked-by: Linus Walleij
    Acked-by: Mark Brown
    Signed-off-by: Greg Kroah-Hartman

    Bill Pemberton
     
  • CONFIG_HOTPLUG is going away as an option so __devinit is no longer
    needed.

    Signed-off-by: Bill Pemberton
    Cc: Srinidhi Kasagar
    Cc: Peter Tyser
    Cc: Daniel Walker
    Cc: Bryan Huntsman
    Acked-by: David Brown
    Acked-by: Mark Brown
    Signed-off-by: Greg Kroah-Hartman

    Bill Pemberton
     

25 Oct, 2012

1 commit

  • In order to make single zImage work for ARM architecture,
    we need to make sure we don't depend on private headers.

    Move USB platform_data to
    and add a minimal drivers/mfd/usb-omap.h.

    Cc: Samuel Ortiz
    Cc: Alan Stern
    Cc: Greg Kroah-Hartman
    Cc: Partha Basak
    Cc: Keshava Munegowda
    Cc: linux-usb@vger.kernel.org
    Signed-off-by: Felipe Balbi
    [tony@atomide.com: updated for local mfd/usb-omap.h]
    Signed-off-by: Tony Lindgren

    Felipe Balbi
     

22 Sep, 2012

2 commits


09 Jul, 2012

1 commit

  • 'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue' (1fcb57d0) fixes
    an issue where the ULPI PHYs were not held in reset while initializing
    the EHCI controller. However, it also changes behavior in
    omap-usb-host.c omap_usbhs_init by releasing reset while the
    configuration in that function was done.

    This change caused a regression on BB-xM where USB would not function
    if 'usb start' had been run from u-boot before booting. A change was
    made to release reset a little bit earlier which fixed the issue on
    BB-xM and did not cause any regressions on 3430 sdp, the board for
    which the fix was originally made.

    This new fix, 'USB: EHCI: OMAP: Finish ehci omap phy reset cycle
    before adding hcd.', (3aa2ae74) caused a regression on OMAP5.

    The original fix to hold the EHCI controller in reset during
    initialization was correct, however it appears that changing
    omap_usbhs_init to not hold the PHYs in reset during it's
    configuration was incorrect. This patch first reverts both fixes, and
    then changes ehci_hcd_omap_probe in ehci-omap.c to hold the PHYs in
    reset as the original patch had done. It also is sure to incorporate
    the _cansleep change that has been made in the meantime.

    I've tested this on Beagleboard xM, I'd really like to get an ack from
    the 3430 sdp and OMAP5 guys before getting this merged.

    v3 - Brown paper bag its too early in the morning actually run
    git commit amend fix
    v2 - Put cansleep gpiolib call outside of spinlock

    Acked-by: Mantesh Sarashetti
    Tested-by: Mantesh Sarashetti
    Acked-by: Keshava Munegowda
    Tested-by: Keshava Munegowda
    Signed-off-by: Russ Dill
    Signed-off-by: Samuel Ortiz

    Russ Dill
     

01 May, 2012

1 commit

  • 'ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue' removes the include for
    linux/gpio.h from omap-usb-host.c. This include indirectly includes plat/cpu.h
    which is required by omap-usb-host.c. Fix the build breakage by including
    it directly.

    Acked-by: Keshava Munegowda
    Acked-by: Kevin Hilman
    Tested-by: Arend van Spriel
    Signed-off-by: Russ Dill
    Signed-off-by: Samuel Ortiz

    Russ Dill
     

17 Apr, 2012

1 commit

  • It is observed that the echi ports of 3430 sdp board
    are not working due to the random timing of programming
    the associated GPIOs of the ULPI PHYs of the EHCI for reset.
    If the PHYs are reset at during usbhs core driver, host ports will
    not work because EHCI driver is loaded after the resetting PHYs.
    The PHYs should be in reset state while initializing the EHCI
    controller.
    The code which does the GPIO pins associated with the PHYs
    are programmed to reset is moved from the USB host core driver
    to EHCI driver.

    Signed-off-by: Keshava Munegowda
    Reviewed-by: Partha Basak
    Acked-by: Felipe Balbi
    Tested-by: Igor Grinberg
    Signed-off-by: Samuel Ortiz

    Keshava Munegowda
     

07 Mar, 2012

2 commits


14 Jan, 2012

1 commit

  • * 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-2.6: (59 commits)
    rtc: max8925: Add function to work as wakeup source
    mfd: Add pm ops to max8925
    mfd: Convert aat2870 to dev_pm_ops
    mfd: Still check other interrupts if we get a wm831x touchscreen IRQ
    mfd: Introduce missing kfree in 88pm860x probe routine
    mfd: Add S5M series configuration
    mfd: Add s5m series irq driver
    mfd: Add S5M core driver
    mfd: Improve mc13xxx dt binding document
    mfd: Fix stmpe section mismatch
    mfd: Fix stmpe build warning
    mfd: Fix STMPE I2c build failure
    mfd: Constify aat2870-core i2c_device_id table
    gpio: Add support for stmpe variant 801
    mfd: Add support for stmpe variant 801
    mfd: Add support for stmpe variant 610
    mfd: Add support for STMPE SPI interface
    mfd: Separate out STMPE controller and interface specific code
    misc: Remove max8997-muic sysfs attributes
    mfd: Remove unused wm831x_irq_data_to_mask_reg()
    ...

    Fix up trivial conflict in drivers/leds/Kconfig due to addition of
    LEDS_MAX8997 and LEDS_TCA6507 next to each other.

    Linus Torvalds
     

09 Jan, 2012

1 commit


16 Dec, 2011

2 commits

  • The usbhs core driver does not enable/disable the interface and
    functional clocks directly, These clocks are handled by runtime pm,
    hence instead of the clock enable/disable, the runtime pm APIS are
    used. however,the optional clocks and port clocks are handled by
    the usbhs core.

    Dependency:
    This patch is dependent on this series:
    [PATCH 0/5 v13 or latest version] omap: usb: host: Runtime PM preparation
    for EHCI and OHCI drivers.

    Validation performed:
    The global suspend/resume of EHCI and OHCI is validated on
    OMAP3430 sdp board with this patch combined with the series:
    [PATCH 0/5 v13 or latest version] omap: usb: host: Runtime PM preparation
    for EHCI and OHCI drivers.

    Signed-off-by: Keshava Munegowda
    Reviewed-by: Kevin Hilman
    Reviewed-by: Partha Basak
    Acked-by: Felipe Balbi
    Acked-by: Samuel Ortiz
    Signed-off-by: Paul Walmsley

    Keshava Munegowda
     
  • device name usbhs clocks are changed from
    usbhs-omap.0 to usbhs_omap; this is because
    in the hwmod registration the device name is set
    as usbhs_omap; The redudant clock nodes are removed.

    Signed-off-by: Keshava Munegowda
    Reviewed-by: Partha Basak
    Signed-off-by: Paul Walmsley

    Keshava Munegowda
     

06 Sep, 2011

2 commits

  • The patch fixes the build failure:

    drivers/mfd/omap-usb-host.c:1034:1: warning: data definition has no type
    or storage class
    drivers/mfd/omap-usb-host.c:1034:1: warning: type defaults to 'int' in
    declaration of 'EXPORT_SYMBOL_GPL'
    drivers/mfd/omap-usb-host.c:1034:1: warning: parameter names (without
    types) in function declaration
    drivers/mfd/omap-usb-host.c:1040:1: warning: data definition has no type
    or storage class
    drivers/mfd/omap-usb-host.c:1040:1: warning: type defaults to 'int' in
    declaration of 'EXPORT_SYMBOL_GPL'
    drivers/mfd/omap-usb-host.c:1040:1: warning: parameter names (without
    types) in function declaration
    drivers/mfd/omap-usb-host.c:1045:13: error: 'THIS_MODULE' undeclared
    here (not in a function)
    drivers/mfd/omap-usb-host.c:1050:15: error: expected declaration
    specifiers or '...' before string constant
    drivers/mfd/omap-usb-host.c:1050:1: warning: data definition has no type
    or storage class
    drivers/mfd/omap-usb-host.c:1050:1: warning: type defaults to 'int' in
    declaration of 'MODULE_AUTHOR'
    drivers/mfd/omap-usb-host.c:1050:15: warning: function declaration isn't
    a prototype
    drivers/mfd/omap-usb-host.c:1051:14: error: expected declaration
    specifiers or '...' before string constant
    drivers/mfd/omap-usb-host.c:1051:1: warning: data definition has no type
    or storage class
    drivers/mfd/omap-usb-host.c:1051:1: warning: type defaults to 'int' in
    declaration of 'MODULE_ALIAS'
    drivers/mfd/omap-usb-host.c:1051:14: warning: function declaration isn't
    a prototype
    drivers/mfd/omap-usb-host.c:1052:16: error: expected declaration
    specifiers or '...' before string constant
    drivers/mfd/omap-usb-host.c:1052:1: warning: data definition has no type
    or storage class
    drivers/mfd/omap-usb-host.c:1052:1: warning: type defaults to 'int' in
    declaration of 'MODULE_LICENSE'
    drivers/mfd/omap-usb-host.c:1052:16: warning: function declaration isn't
    a prototype
    drivers/mfd/omap-usb-host.c:1053:20: error: expected declaration
    specifiers or '...' before string constant
    drivers/mfd/omap-usb-host.c:1053:1: warning: data definition has no type
    or storage class
    drivers/mfd/omap-usb-host.c:1053:1: warning: type defaults to 'int' in
    declaration of 'MODULE_DESCRIPTION'
    drivers/mfd/omap-usb-host.c:1053:20: warning: function declaration isn't
    a prototype
    make[2]: *** [drivers/mfd/omap-usb-host.o] Error 1
    CC fs/proc/namespaces.o
    make[1]: *** [drivers/mfd] Error 2
    make: *** [drivers] Error 2
    make: *** Waiting for unfinished jobs....

    Signed-off-by: Ming Lei
    Signed-off-by: Samuel Ortiz

    Ming Lei
     
  • This code section seems to have been accidentally copy pasted.
    It causes incorrect bits to be set up in the TLL_CHANNEL_CONF
    register and prevents the TLL mode from working correctly.

    Cc: stable@kernel.org
    Signed-off-by: Anand Gadiyar
    Cc: Keshava Munegowda
    Acked-by: Felipe Balbi
    Signed-off-by: Samuel Ortiz

    Anand Gadiyar
     

01 Aug, 2011

1 commit

  • usbhs_disable function was invoking clk_enable() instead of
    clk_disable(), thus only increasing the clock usage counter and
    preventing this particular clock from being ever turned off.
    Because of this, the power domain of omap4 the USB Host subsystem
    would never reach lower power states.This patch calls clk_disable()
    in usbhs_disable function

    Signed-off-by: Keshava Munegowda
    Signed-off-by: Samuel Ortiz

    Keshava Munegowda
     

05 Jul, 2011

1 commit

  • This reverts commit 7e6502d577106fb5b202bbaac64c5f1b065e6daa.

    Oops are produced during initialization of ehci and ohci
    drivers. This is because the run time pm apis are used by
    the driver but the corresponding hwmod structures and
    initialization is not merged. hence revering back the
    commit id 7e6502d577106fb5b202bbaac64c5f1b065e6daa

    Signed-off-by: Keshava Munegowda
    Reported-by: Luciano Coelho
    Acked-by: Felipe Balbi
    Signed-off-by: Samuel Ortiz

    Keshava Munegowda
     

27 May, 2011

1 commit

  • The usbhs core driver does not enable/disable the interface and
    functional clocks; These clocks are handled by hwmod and runtime pm,
    hence insted of the clock enable/disable, the runtime pm APIS are
    used. however,the port clocks and tll clocks are handled
    by the usbhs core.

    Signed-off-by: Keshava Munegowda
    Signed-off-by: Samuel Ortiz

    Keshava Munegowda