1. 23 5月, 2011 1 次提交
  2. 04 4月, 2011 1 次提交
  3. 22 3月, 2011 1 次提交
  4. 19 3月, 2011 1 次提交
    • B
      ARM: OMAP2+: Fix warnings for GPMC interrupt · 77aded2f
      Balaji T K 提交于
      Commit db97eb7d
      (omap: gpmc: enable irq mode in gpmc) enabled interrupts for
      GPMC (General Purpose Memory Controller). However, looks like
      this patch only works on omap3. Fix the issues to avoid warnings
      on omap4 during the boot.
      
      GPMC: number of chip select is 8, CS0 to CS7. One less IRQ
      allocated throws below warning at boot:
      
      [    0.429290] Trying to install type control for IRQ409
      [    0.429290] Trying to set irq flags for IRQ409
      
      Resolve following warning messages in boot when irq chip is not set:
      
      [    0.429229] Trying to install interrupt handler for IRQ402
      [    0.429229] Trying to install interrupt handler for IRQ403
      [    0.429229] Trying to install interrupt handler for IRQ404
      [    0.429260] Trying to install interrupt handler for IRQ405
      [    0.429260] Trying to install interrupt handler for IRQ406
      [    0.429260] Trying to install interrupt handler for IRQ407
      [    0.429290] Trying to install interrupt handler for IRQ408
      
      Resolve following warning in OMAP4:
      [    0.429290] gpmc: irq-20 could not claim: err -22
      Signed-off-by: NBalaji T K <balajitk@ti.com>
      [tony@atomide.com: combined patches into one, updated comments]
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      77aded2f
  5. 16 3月, 2011 1 次提交
  6. 15 3月, 2011 1 次提交
    • D
      omap: iovmm: don't check 'da' to set IOVMF_DA_FIXED flag · d038aee2
      David Cohen 提交于
      Currently IOVMM driver sets IOVMF_DA_FIXED/IOVMF_DA_ANON flags according
      to input 'da' address when mapping memory:
      da == 0: IOVMF_DA_ANON
      da != 0: IOVMF_DA_FIXED
      
      It prevents IOMMU to map first page with fixed 'da'. To avoid such
      issue, IOVMM will not automatically set IOVMF_DA_FIXED. It should now
      come from the user throught 'flags' parameter when mapping memory.
      As IOVMF_DA_ANON and IOVMF_DA_FIXED are mutually exclusive, IOVMF_DA_ANON
      can be removed. The driver will now check internally if IOVMF_DA_FIXED
      is set or not.
      Signed-off-by: NDavid Cohen <dacohen@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      d038aee2
  7. 12 3月, 2011 1 次提交
  8. 11 3月, 2011 5 次提交
  9. 10 3月, 2011 5 次提交
  10. 09 3月, 2011 1 次提交
  11. 08 3月, 2011 3 次提交
  12. 02 3月, 2011 3 次提交
  13. 01 3月, 2011 7 次提交
  14. 28 2月, 2011 1 次提交
  15. 26 2月, 2011 2 次提交
    • R
      OMAP4: DPLL: Add dpll api to control GATE_CTRL · 97f67898
      Rajendra Nayak 提交于
      On OMAP4, the dpll post divider outputs (MX outputs)
      along with clockout_x2 output provide a way to allow/deny
      hardware level autogating.
      Allowing autoidle would mean that the hw would autogate
      this clock when there is no dependency for it.
      Denying idle would mean that this clock output will be
      forced to stay enabled.
      
      Add dpll api's to read/allow/deny idle control
      for these dpll mx postdividers.
      
      NOTE: The gatectrl bit set to 0 allows gatectrl,
      and the bit set to 1 denies gatectrl.
      Signed-off-by: NRajendra Nayak <rnayak@ti.com>
      [paul@pwsan.com: moved OMAP4-specific DPLL control code to
       mach-omap2/dpll44xx.c; added some documentation for CLOCK_CLKOUTX2]
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      97f67898
    • R
      OMAP: clock: Add allow_idle/deny_idle support in clkops · 58e846fe
      Rajendra Nayak 提交于
      On OMAP various clock nodes (dpll's, mx post dividers, interface clocks)
      support hardware level autogating which can be controlled from
      software.
      Support such functionality by adding two new function pointer
      allow_idle and deny_idle in the clkops structure.
      
      These function pointers can be populated for any clock
      node which supports hardware level autogating.
      
      Also add 2 new functions (omap_clk_enable_autoidle_all and
      omap_clk_disable_autoidle_all) which can be called from
      architecture specific PM core code, if hardware level
      autogating (for all supported clock nodes) is to be
      enabled or disabled.
      Signed-off-by: NRajendra Nayak <rnayak@ti.com>
      [paul@pwsan.com: use spinlock rather than mutex due to race; renamed functions;
       functions now return ints]
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      58e846fe
  16. 25 2月, 2011 6 次提交
新手
引导
客服 返回
顶部