1. 21 6月, 2011 3 次提交
    • N
      OMAP3+: SR: enable/disable SR only on need · ac77a6f7
      Nishanth Menon 提交于
      Since we already know the state of the autocomp enablement, we can
      see if the requested state is different from the current state and
      enable/disable SR only on the need basis.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NKevin Hilman <khilman@ti.com>
      ac77a6f7
    • N
      OMAP3+: SR: disable interrupt by default · 1279ba59
      Nishanth Menon 提交于
      We will enable and disable interrupt on a need basis in the class
      driver. We need to keep the IRQ disabled by default else the
      forceupdate or vcbypass events could trigger events that we don't
      need/expect to handle.
      
      This is a preparation for SmartReflex AVS class drivers such as
      class 2 and class 1.5 which would need to use interrupts. Existing
      SmartReflex AVS class 3 driver does not require to use interrupts
      and is not impacted by this change.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NKevin Hilman <khilman@ti.com>
      1279ba59
    • N
      OMAP3+: SR: make notify independent of class · 7a89afa8
      Nishanth Menon 提交于
      Interrupt notification mechanism of SmartReflex can be used by the
      choice of implementation of the class driver. For example, Class 2 and
      Class 1.5 of SmartReflex can both use the interrupt notification to
      identify the transition of voltage or other events.
      
      Hence, the actual class does not matter for notifier. Let the class
      driver's handling decide how it should be used. SmartReflex driver
      should provide just the primitives.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NKevin Hilman <khilman@ti.com>
      7a89afa8
  2. 14 6月, 2011 11 次提交
  3. 13 6月, 2011 8 次提交
  4. 12 6月, 2011 15 次提交
  5. 11 6月, 2011 3 次提交