1. 21 1月, 2017 1 次提交
    • A
      ARM: OMAP3: Fix SoC detection of OMAP36/37 Family · 631af44c
      Adam Ford 提交于
      The OMAP36/37 families are similar, but there are a few features sections
      that can help identify some of them.  Let's add checks for 3630/3730,
      OMAP3621, DM3725, OMAP3615/DM3715, OMAP3611, and AM3703 all based on
      features similar to what was done for the OMAP34xx/35xx series
      
      The checkpatch flags some warnings for braces, but I kept the coding style
      to match the adjacent code for consistency.
      
      I don't have an OMAP36xx to test, but this was tested on both a DM3730 and
      AM3703.
      Signed-off-by: NAdam Ford <aford173@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      631af44c
  2. 08 11月, 2016 1 次提交
  3. 19 4月, 2016 1 次提交
  4. 09 4月, 2016 1 次提交
  5. 31 3月, 2016 1 次提交
  6. 23 12月, 2015 1 次提交
    • T
      ARM: OMAP2+: Fix SoC detection for dra62x j5-eco · 68b813bf
      Tony Lindgren 提交于
      We can boot dra62x j5-eco using the dm814x code as the clocks and
      devices are mapped in the device tree. The dra62x is also known
      as jacinto 5 eco.
      
      We may want to add separate soc_is macros for dra62x if needed,
      but this gets us to the point where we can boot dra62x with just
      dts changes.
      
      Let's also print out the unknown hawkeye register to make things
      a bit easier for new SoC variants.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      68b813bf
  7. 17 10月, 2015 1 次提交
  8. 02 9月, 2015 1 次提交
    • V
      ARM: DRA752: Add ID detect for ES2.0 · 81032e34
      Vishal Mahaveer 提交于
      ES2.0 is a minor variant of ES1.1. ES2.0 is an incremental revision
      with various fixes including the following:
      	- reset logic fixes
      	- few assymetric aging logic fixes
      	- MMC clock rate fixes
      	- Ethernet speed fixes
      	- edma fixes for mcasp
      
      NOTE: even though we use a compatible of dra742 and dra752, the usage in
      the Linux kernel is more or less interchangable - we use dra752 more
      often in the linux kernel compared to dra742 and 4.2-rc6
      Signed-off-by: NVishal Mahaveer <vishalm@ti.com>
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      81032e34
  9. 01 4月, 2015 1 次提交
  10. 17 3月, 2015 1 次提交
  11. 15 1月, 2015 1 次提交
    • T
      ARM: OMAP2+: Fix ti81xx devtype · e226ebe9
      Tony Lindgren 提交于
      Otherwise we get error "Cannot detect omap type!" and many
      things can fail with following:
      
      Unhandled fault: imprecise external abort (0xc06) at 0xc6031fb0
      
      This is because the omap_type is being used to set up th SoC
      specific functions for omaps.
      
      Cc: Brian Hutchinson <b.hutchman@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      e226ebe9
  12. 11 12月, 2014 1 次提交
  13. 26 8月, 2014 1 次提交
  14. 16 6月, 2014 1 次提交
  15. 20 5月, 2014 1 次提交
  16. 08 5月, 2014 1 次提交
  17. 01 3月, 2014 2 次提交
  18. 09 10月, 2013 1 次提交
    • N
      ARM: OMAP5: id: Remove ES1.0 support · aa2f4b16
      Nishanth Menon 提交于
      OMAP5 ES1.0 was intended as a test chip and has major register level
      differences w.r.t ES2.0 revision of the chip. All register defines,
      dts support has been solely added for ES2.0 version of the chip.
      Further, all ES1.0 chips and platforms are supposed to have been
      removed from circulation. Hence, there is no need to further retain
      any resemblence of ES1.0 support in id detection code.
      
      Remove the omap_revision handling and BUG() instead to prevent folks
      who mistakenly try an older unsupported chip and report bogus errors.
      Signed-off-by: NNishanth Menon <nm@ti.com>
      Acked-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      aa2f4b16
  19. 04 10月, 2013 1 次提交
  20. 13 8月, 2013 1 次提交
  21. 18 6月, 2013 2 次提交
  22. 12 6月, 2013 3 次提交
  23. 10 5月, 2013 1 次提交
    • T
      ARM: OMAP2+: Remove bogus IS_ERR_OR_NULL checking from id.c · b1dd11d6
      Tony Lindgren 提交于
      Commit 6770b211 (ARM: OMAP2+: Export SoC information to userspace)
      had some broken return value handling as noted by Russell King:
      
      +       soc_dev = soc_device_register(soc_dev_attr);
      +       if (IS_ERR_OR_NULL(soc_dev)) {
      +               kfree(soc_dev_attr);
      +               return;
      +       }
      +
      +       parent = soc_device_to_device(soc_dev);
      +       if (!IS_ERR_OR_NULL(parent))
      +               device_create_file(parent, &omap_soc_attr);
      
      This is nonsense.  For the first, IS_ERR() is sufficient.  For the second,
      tell me what error checking is required in the return value of this
      function:
      
      struct device *soc_device_to_device(struct soc_device *soc_dev)
      {
              return &soc_dev->dev;
      }
      
      when you've already determined that the passed soc_dev is a valid pointer.
      If you read the comments against the prototype:
      
      /**
       * soc_device_to_device - helper function to fetch struct device
       * @soc: Previously registered SoC device container
       */
      struct device *soc_device_to_device(struct soc_device *soc);
      
      if "soc" is valid, it means the "previously registered SoC device container"
      must have succeeded and that can only happen if the struct device has been
      registered.  Ergo, there will always be a valid struct device pointer for
      any registered SoC device container.  Therefore, if soc_device_register()
      succeeds, then the return value from soc_device_to_device() will always be
      valid and no error checking of it is required.
      
      Simples.  The rule as ever applies here: get to know the APIs your using
      and don't fumble around in the dark hoping that you'll get this stuff
      right.
      
      Fix it as noted by Russell.
      Reported-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b1dd11d6
  24. 09 5月, 2013 1 次提交
  25. 09 4月, 2013 2 次提交
  26. 19 3月, 2013 1 次提交
  27. 02 2月, 2013 1 次提交
  28. 01 2月, 2013 1 次提交
  29. 15 11月, 2012 1 次提交
  30. 09 11月, 2012 1 次提交
  31. 21 9月, 2012 1 次提交
  32. 13 9月, 2012 1 次提交
    • T
      ARM: OMAP: Split plat/hardware.h, use local soc.h for omap2+ · dbc04161
      Tony Lindgren 提交于
      As the plat and mach includes need to disappear for single zImage work,
      we need to remove plat/hardware.h.
      
      Do this by splitting plat/hardware.h into omap1 and omap2+ specific files.
      
      The old plat/hardware.h already has omap1 only defines, so it gets moved
      to mach/hardware.h for omap1. For omap2+, we use the local soc.h
      that for now just includes the related SoC headers to keep this patch more
      readable.
      
      Note that the local soc.h still includes plat/cpu.h that can be dealt
      with in later patches. Let's also include plat/serial.h from common.h for
      all the board-*.c files. This allows making the include files local later
      on without patching these files again.
      
      Note that only minimal changes are done in this patch for the
      drivers/watchdog/omap_wdt.c driver to keep things compiling. Further
      patches are needed to eventually remove cpu_is_omap usage in the drivers.
      
      Also only minimal changes are done to sound/soc/omap/* to remove the
      unneeded includes and to define OMAP44XX_MCPDM_L3_BASE locally so there's
      no need to include omap44xx.h.
      
      While at it, also sort some of the includes in the standard way.
      
      Cc: linux-watchdog@vger.kernel.org
      Cc: alsa-devel@alsa-project.org
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Cc: Jarkko Nikula <jarkko.nikula@bitmer.com>
      Cc: Liam Girdwood <lrg@ti.com>
      Acked-by: NWim Van Sebroeck <wim@iguana.be>
      Acked-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      dbc04161
  33. 12 9月, 2012 1 次提交
    • P
      ARM: OMAP: unwrap strings · 7852ec05
      Paul Walmsley 提交于
      Find and unwrap wrapped strings in the style:
      
      	pr_debug("clockdomain: hardware cannot set/clear wake up of "
      		 "%s when %s wakes up\n", clkdm1->name, clkdm2->name);
      
      Keeping these strings contiguous seems to be the current Linux kernel
      policy.
      
      The offending lines were found with the following command:
      
          pcregrep -rnM '"\s*$\s*"' arch/arm/*omap*
      
      While here, some messages have been clarified, some pr_warning(
      ... calls have been converted to pr_warn( ..., and some printk(KERN_*
      ... have been converted to pr_*.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      7852ec05
  34. 09 7月, 2012 1 次提交
  35. 05 7月, 2012 1 次提交