1. 14 Sep, 2011 1 commit
    • Paul Walmsley's avatar
      OMAP3: id: remove identification codes that only correspond to marketing names · 1f1b0353
      Paul Walmsley authored
      The OMAP3505/AM3505 appears to be based on the same silicon as the
      OMAP3517/AM3517, with some features disabled via eFuse bits.  Follow
      the same practice as OMAP3430 and identify these devices internally as
      part of the OMAP3517/AM3517 family.
      
      The OMAP3503/3515/3525/3530 chips appear to be based on the same silicon
      as the OMAP3430, with some features disabled via eFuse bits.  Identify
      these devices internally as part of the OMAP3430 family.
      
      Remove the old OMAP35XX_CLASS, which actually covered two very different
      chip families.  The OMAP3503/3515/3525/3530 chips will now be covered by
      OMAP343X_CLASS, since the silicon appears to be identical.  For the
      OMAP3517/AM3517 family, create a new class, OMAP3517_CLASS.
      
      Thanks to Tony Lindgren <tony@atomide.com> for some help with the second
      revision of this patch.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Sanjeev Premi <premi@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Tested-by: default avatarIgor Grinberg <grinberg@compulab.co.il>
      Tested-by: default avatarAbhilash Koyamangalath <abhilash.kv@ti.com>
      1f1b0353
  2. 05 Sep, 2011 2 commits
    • Paul Walmsley's avatar
      Merge branches 'non_hwmod_compliant_fix_3.1rc', 'omap3_clock_fixes_3.1rc',... · 87635501
      Paul Walmsley authored
      Merge branches 'non_hwmod_compliant_fix_3.1rc', 'omap3_clock_fixes_3.1rc', 'omap4_clock_fixes_3.1rc', 'missing_2430_musb_adds_terminator_fix_3.1rc' and 'pwrdm_clkdm_fixes_3.1rc' into prcm-fixes-a-3.1rc
      87635501
    • Paul Walmsley's avatar
      OMAP2430: hwmod: musb: add missing terminator to omap2430_usbhsotg_addrs[] · 10167873
      Paul Walmsley authored
      Add a missing array terminator to omap2430_usbhsotg_addrs[].  Without
      this terminator, the omap_hwmod resource building code runs off the
      end of the array, resulting in at least this error -- if not worse
      behavior:
      
      [    0.578002] musb-omap2430: failed to claim resource 4
      [    0.583465] omap_device: musb-omap2430: build failed (-16)
      [    0.589294] Could not build omap_device for musb-omap2430 usb_otg_hs
      
      This should have been part of commit
      78183f3f ("omap_hwmod: use a null
      structure record to terminate omap_hwmod_addr_space arrays") but was
      evidently missed.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      10167873
  3. 29 Aug, 2011 1 commit
  4. 28 Aug, 2011 1 commit
  5. 27 Aug, 2011 2 commits
  6. 26 Aug, 2011 13 commits
  7. 25 Aug, 2011 20 commits