1. 21 9月, 2019 1 次提交
  2. 17 5月, 2018 1 次提交
  3. 01 5月, 2018 1 次提交
    • T
      ARM: OMAP2+: Use signed value for sysc register offsets · 103fd8e7
      Tony Lindgren 提交于
      We currently don't know if a revision register exists or not. Zero is
      often a valid offset for the revision register. As we are still checking
      device tree data against platform data, we will get bogus warnings with
      correct device tree data because of incomplete platform data.
      
      Let's fix the issue by using signed offsets and tag the revision registers
      that don't exist with -ENODEV, and init the missing ones with the correct
      revision register offset.
      
      Cc: Paul Walmsley <paul@pwsan.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      103fd8e7
  4. 15 2月, 2018 5 次提交
    • S
      ARM: OMAP2+: Cleanup omap_mcbsp_dev_attr and other legacy data · 0693036c
      Suman Anna 提交于
      The omap_mcbsp_dev_attr data was used to supply instance-specific
      data for legacy non-DT devices. The legacy McBSP device support
      including the usage of the hwmod class revision data has been
      dropped in commit 48f66937 ("ARM: OMAP2+: Remove unused legacy
      code for McBSP") and this data is therefore no longer needed.
      So, cleanup the structure and all the associated data in various
      hwmod data files.
      
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      0693036c
    • S
      ARM: OMAP2+: Cleanup omap2_spi_dev_attr and other legacy data · 1cddc364
      Suman Anna 提交于
      The omap2_spi_dev_attr data was used to supply instance-specific
      data for legacy non-DT devices. The SPI legacy device support
      including the usage of the hwmod class revision data has been
      dropped in commit 6f3ab009 ("ARM: OMAP2+: Remove unused legacy
      code for device init") and this data is therefore no longer needed.
      So, cleanup the structure and all the associated data in various
      hwmod data files.
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      1cddc364
    • S
      ARM: OMAP2+: Cleanup omap_timer_capability_dev_attr usage · cc7e3fb6
      Suman Anna 提交于
      The omap_timer_capability_dev_attr data was used to supply instance
      specific capabilities (like always-on, PWM functionality or ability
      to interrupt DSP cores) for legacy non-DT devices. These capabilities
      are now provided through device-tree properties. The legacy device
      support has been cleaned up in commit 8d39ff3d ("ARM: OMAP2+:
      Remove unused legacy code for timer") and this data is therefore
      no longer needed. So, cleanup the structure and all the associated
      data in various hwmod data files.
      
      While at this, remove the stale header in hwmod data files that
      already do not have any timer capability data.
      
      Cc: Keerthy <j-keerthy@ti.com>
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      cc7e3fb6
    • S
      ARM: OMAP2+: Cleanup omap_i2c_dev_attr usage · 5297e1d7
      Suman Anna 提交于
      The omap_i2c_dev_attr data was used to supply instance-specific
      data for legacy non-DT devices. The I2C legacy device support has
      been cleaned up in commit 65fa3e71 ("ARM: OMAP2+: Remove legacy
      i2c.c platform init code") and this data is therefore no longer
      needed. So, cleanup the structure and all the associated data in
      various hwmod data files.
      
      The i2c-omap.h header is still needed because of the need for
      various OMAP_I2C_IP_VERSION_x macros.
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      5297e1d7
    • S
      ARM: OMAP2+: Cleanup omap_gpio_dev_attr usage · a0e37da2
      Suman Anna 提交于
      The omap_gpio_dev_attr data was used to supply instance-specific
      data for legacy non-DT devices. The GPIO legacy device support has
      been cleaned up in commit 14944934 ("ARM: OMAP2+: Remove legacy
      gpio code") a while ago and this data is therefore no longer needed.
      So, cleanup the structure and all the associated data in various
      hwmod data files.
      Signed-off-by: NSuman Anna <s-anna@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      a0e37da2
  5. 21 12月, 2017 2 次提交
  6. 11 10月, 2017 2 次提交
    • T
      ARM: OMAP2+: Drop legacy struct omap_hwmod_addr_space · 9cffb1a0
      Tony Lindgren 提交于
      With all of mach-omap2 booting now in device tree only mode,
      we can get the module IO range from device tree and just drop
      the legacy hwmod struct omap_hwmod_addr_space.
      
      Cc: Lokesh Vutla <lokeshvutla@ti.com>
      Cc: Paul Walmsley <paul@pwsan.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      9cffb1a0
    • T
      ARM: OMAP2+: Drop omap_hwmod_dma_info · c2b84a9b
      Tony Lindgren 提交于
      We have all of mach-omap2 booting in device tree only
      mode now, and this data is populated from device tree.
      
      Note that once we have removed support for the omap legacy
      DMA, we can also drop struct omap_dma_dev_attr.
      
      Cc: Lokesh Vutla <lokeshvutla@ti.com>
      Cc: Paul Walmsley <paul@pwsan.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      c2b84a9b
  7. 20 9月, 2017 1 次提交
  8. 15 8月, 2017 1 次提交
  9. 29 3月, 2017 2 次提交
  10. 15 3月, 2017 1 次提交
  11. 10 11月, 2016 5 次提交
  12. 10 6月, 2016 2 次提交
  13. 11 4月, 2016 4 次提交
  14. 01 3月, 2016 1 次提交
  15. 25 2月, 2016 1 次提交
  16. 09 2月, 2016 2 次提交
  17. 01 12月, 2015 1 次提交
  18. 13 11月, 2015 1 次提交
  19. 24 10月, 2015 2 次提交
  20. 20 10月, 2015 1 次提交
  21. 16 7月, 2015 1 次提交
  22. 04 6月, 2015 2 次提交