27 May, 2011

1 commit

  • The charger fault IRQs from the twl will in future patches be handled
    by a seperate IRQ handler in the charger driver than the general charger
    IRQ. Give them different IRQ numbers now to allow the charger driver to
    be merged in the future.

    Signed-off-by: Graeme Gregory
    Signed-off-by: Samuel Ortiz

    Graeme Gregory
     

31 Mar, 2011

1 commit


27 Mar, 2011

2 commits


14 Jan, 2011

1 commit


10 Dec, 2010

1 commit

  • With TWL6030-usb, VBUS SESS_VLD and SESS_END events are not generated
    as expected. When these interrupts are enabled, charger VBUS detection
    interrupt does not get generated. So USBOTG has to be dependent on charger
    VBUS interrupts.
    So added one bit for USBOTG and changed the handler to call the
    USBOTG handler whenever there is a charger VBUS interrpt.

    VBUS SESS_VLD and SESS_END event generation issue is under debug with
    HW team. This fix might not be required once after fixing the issue.

    Signed-off-by: Balaji TK
    Signed-off-by: Hema HK
    Cc: Samuel Ortiz
    Signed-off-by: Felipe Balbi

    Hema HK
     

29 Oct, 2010

2 commits

  • Fixes following sparse warnings for twl4030 and twl6030 irq files.

    drivers/mfd/twl4030-irq.c:783:5: warning: symbol 'twl4030_init_irq' was not
    declared. Should it be static?
    drivers/mfd/twl4030-irq.c:863:5: warning: symbol 'twl4030_exit_irq' was not
    declared. Should it be static?
    drivers/mfd/twl4030-irq.c:873:5: warning: symbol 'twl4030_init_chip_irq' was
    not declared. Should it be static?

    drivers/mfd/twl6030-irq.c:226:5: warning: symbol 'twl6030_init_irq' was not
    declared. Should it be static?
    drivers/mfd/twl6030-irq.c:290:5: warning: symbol 'twl6030_exit_irq' was not
    declared. Should it be static?

    Signed-off-by: G, Manjunath Kondaiah
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: Tony Lindgren
    Cc: Nishanth Menon
    Signed-off-by: Samuel Ortiz

    G, Manjunath Kondaiah
     
  • Adding card detect callback function and card detect configuration
    function for MMC1 Controller on OMAP4.

    Card detect configuration function does initial configuration of the
    MMC Control & PullUp-PullDown registers of Phoenix.

    For MMC1 Controller, card detect interrupt source is
    twl6030 which is non-gpio. The card detect call back function provides
    card present/absent status by reading MMC Control register present
    on twl6030.

    Since OMAP4 doesn't use any GPIO line as used in OMAP3 for card detect,
    the suspend/resume initialization which was done in omap_hsmmc_gpio_init
    previously is moved to the probe thus making it generic for both OMAP3 &
    OMAP4.

    Cc: Tony Lindgren
    Cc: Andrew Morton
    Cc: Madhusudhan Chikkature
    Cc: Adrian Hunter
    Signed-off-by: Kishore Kadiyala
    Signed-off-by: Samuel Ortiz

    kishore kadiyala
     

14 Dec, 2009

1 commit

  • This patch adds support for phoenix interrupt framework. New iInterrupt
    status register A, B, C are introduced in Phoenix and are cleared on write.
    Due to the differences in interrupt handling with respect to TWL4030,
    twl6030-irq.c is created for TWL6030 PMIC

    Signed-off-by: Rajendra Nayak
    Signed-off-by: Balaji T K
    Signed-off-by: Santosh Shilimkar
    Reviewed-by: Tony Lindgren
    Signed-off-by: Samuel Ortiz

    Balaji T K