1. 20 9月, 2017 11 次提交
    • T
      ARM: dts: Add missing hwmod related properties for dra7 · 288cdbbf
      Tony Lindgren 提交于
      On dra7 we're missing two "ti,hwmods" properties that the SoC
      interconnect code needs. For hdq 1-wire, we need to add the
      node for that.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      Cc: Nishanth Menon <nm@ti.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      288cdbbf
    • T
      ARM: dts: Add missing hwmod related nodes for am33xx · cd57dc5a
      Tony Lindgren 提交于
      On am33xx we're missing the pmu and emif nodes with their related
      "ti,hwmods" properties that the SoC interconnect code needs.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      Let's also update the related binding documentation while at it.
      
      Cc: Mark Rutland <mark.rutland@arm.com>
      Acked-by: NRob Herring <robh+dt@kernel.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      cd57dc5a
    • T
      ARM: dts: Add missing dma hwmod property for omap5 · ef90bfb8
      Tony Lindgren 提交于
      On omap5 we're missing the dma "ti,hwmods" property that the
      SoC interconnect code needs.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      ef90bfb8
    • T
      ARM: dts: Add missing wdt3 node for omap4 · 5750d671
      Tony Lindgren 提交于
      On omap4 we're missing the wdt3 node with it's related "ti,hwmods"
      property that the SoC interconnect code needs.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      5750d671
    • T
      ARM: dts: Add missing hsi node for omap4 · 8be8576f
      Tony Lindgren 提交于
      On omap4 we're missing the hsi node with it's related "ti,hwmods"
      property that the SoC interconnect code needs.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      Let's also update the binding accrodingly while at it.
      
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Rob Herring <robh+dt@kernel.org>
      Reviewed-by: NSebastian Reichel <sre@kernel.org>
      Acked-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      8be8576f
    • T
      ARM: dts: Add missing onewire node for omap4 · d6e1a238
      Tony Lindgren 提交于
      On omap4 we're missing the onewire node with it's related "ti,hwmods"
      property that the SoC interconnect code needs.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      d6e1a238
    • T
      ARM: dts: Add missing smartreflex node and binding for omap4 · 514b2da4
      Tony Lindgren 提交于
      We are missing smartreflex device tree nodes for omap4 with
      their related "ti,hwmods" properties that the SoC interconnect
      code needs.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      And since we're missing the device tree binding for smartreflex,
      let's also add it and document the existing omap3 use too.
      
      Note that the related driver also needs to be updated to probe
      using device tree and get the platform data passed to it using
      auxdata with arch/arm/mach-omap2/pdata-quirks.c.
      
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Nishanth Menon <nm@ti.com>
      Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
      Cc: Tero Kristo <t-kristo@ti.com>
      Acked-by: NRob Herring <robh+dt@kernel.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      514b2da4
    • T
      ARM: dts: Add missing hwmods property for omap4 dma · 370ad6b4
      Tony Lindgren 提交于
      On omap4, we are missing a ti,hwmods property for dma that the
      that the SoC interconnect code needs.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      370ad6b4
    • T
      ARM: dts: Add missing properties for omap4 control modules · 1d6a332a
      Tony Lindgren 提交于
      On omap4, we are missing several ti,hwmods properties and IO
      ranges for system control modules. These are needed by the SoC
      interconnect code.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      In order to add these, we need to move omap4_pmx_wkup to be a
      child of omap4_padconf_wkup.
      
      On omap4 there are separate modules for control module and
      control module pads. For control module core, we have this
      already configured except for the missing ti,hwmods and reg
      entries.
      
      Cc: Mark Rutland <mark.rutland@arm.com>
      Acked-by: NRob Herring <robh+dt@kernel.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      1d6a332a
    • T
      ARM: dts: Configure pmu without interrupt for omap4430 · b0142a10
      Tony Lindgren 提交于
      On omap4430, the PMU is not configure unlike on omap4460 because
      of the missing handling.
      
      The missing pmu node with the missing ti,hwmods entry will cause
      boot time errors when the legacy platform data is removed as
      the SoC interconnect code needs it.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      Let's fix the issue by configuring PMU but without the interrupts.
      Then when cross trigger interface (CTI) is supported, we can add
      interrupts also for omap4430.
      
      Cc: Jon Hunter <jonathanh@nvidia.com>
      Cc: Will Deacon <will.deacon@arm.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      b0142a10
    • T
      ARM: dts: Add missing dma hwmods property for omap3 · f0f838fd
      Tony Lindgren 提交于
      On omap3, we are missing a ti,hwmods property for dma that
      the SoC interconnect code needs.
      
      Note that this will only show up as a bug with "doesn't have
      mpu register target base" boot errors when the legacy platform
      data is removed.
      
      Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      f0f838fd
  2. 15 9月, 2017 13 次提交
  3. 14 9月, 2017 15 次提交
  4. 13 9月, 2017 1 次提交
新手
引导
客服 返回
顶部