1. 16 Jul, 2020 2 commits
  2. 14 Jul, 2020 4 commits
    • Tony Lindgren's avatar
      ARM: OMAP2+: Drop legacy platform data for omap5 usb host · cca3f3e6
      Tony Lindgren authored
      We can now probe devices with ti-sysc interconnect driver and dts
      data. Let's drop the related platform data and custom ti,hwmods
      dts property.
      
      As we're just dropping data, and the early platform data init
      is based on the custom ti,hwmods property, we want to drop both
      the platform data and ti,hwmods property in a single patch.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      cca3f3e6
    • Tony Lindgren's avatar
      ARM: OMAP2+: Drop legacy platform data for omap4 usb · 509b1377
      Tony Lindgren authored
      We can now probe devices with ti-sysc interconnect driver and dts
      data. Let's drop the related platform data and custom ti,hwmods
      dts property.
      
      As we're just dropping data, and the early platform data init
      is based on the custom ti,hwmods property, we want to drop both
      the platform data and ti,hwmods property in a single patch.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      509b1377
    • Tony Lindgren's avatar
      ARM: OMAP2+: Drop legacy platform data for dra7 dwc3 · c7b72abc
      Tony Lindgren authored
      We can now probe devices with ti-sysc interconnect driver and dts
      data. Let's drop the related platform data and custom ti,hwmods
      dts property.
      
      As we're just dropping data, and the early platform data init
      is based on the custom ti,hwmods property, we want to drop both
      the platform data and ti,hwmods property in a single patch.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      c7b72abc
    • Tony Lindgren's avatar
      ARM: OMAP2+: Drop legacy platform data for omap5 dwc3 · 0db53013
      Tony Lindgren authored
      We can now probe devices with ti-sysc interconnect driver and dts
      data. Let's drop the related platform data and custom ti,hwmods
      dts property.
      
      As we're just dropping data, and the early platform data init
      is based on the custom ti,hwmods property, we want to drop both
      the platform data and ti,hwmods property in a single patch.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      0db53013
  3. 13 Jul, 2020 21 commits
    • Alexander A. Klimov's avatar
      Replace HTTP links with HTTPS ones: OMAP DEVICE TREE SUPPORT · 75f66813
      Alexander A. Klimov authored
      Rationale:
      Reduces attack surface on kernel devs opening the links for MITM
      as HTTPS traffic is much harder to manipulate.
      
      Deterministic algorithm:
      For each file:
        If not .svg:
          For each line:
            If doesn't contain `\bxmlns\b`:
              For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
      	  If neither `\bgnu\.org/license`, nor `\bmozilla\.org/MPL\b`:
                  If both the HTTP and HTTPS versions
                  return 200 OK and serve the same content:
                    Replace HTTP with HTTPS.
      Signed-off-by: default avatarAlexander A. Klimov <grandmaster@al2klimov.de>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      75f66813
    • Suman Anna's avatar
      ARM: dts: omap5-uevm: Add watchdog timers for IPU and DSP · e94828c1
      Suman Anna authored
      The watchdog timers have been added for the IPU and DSP remoteproc
      devices for the OMAP5 uEVM board. The following timers (same as the
      timers on OMAP4 Panda boards) are used as the watchdog timers,
              DSP : GPT6
              IPU : GPT9 & GPT11 (one for each Cortex-M4 core)
      
      The MPU-side drivers will use this data to initialize the watchdog
      timers, and listen for any watchdog triggers. The BIOS-side code
      needs to configure and refresh these timers properly to not throw
      a watchdog error.
      
      These timers can be changed or removed as per the system integration
      needs, alongside appropriate equivalent changes on the firmware side.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      e94828c1
    • Suman Anna's avatar
      ARM: dts: omap4-panda-common: Add watchdog timers for IPU and DSP · f1c4a33f
      Suman Anna authored
      The watchdog timers have been added for the IPU and DSP remoteproc
      devices on all the OMAP4-based Panda boards. The following timers
      are used as the watchdog timers,
      	DSP : GPT6
      	IPU : GPT9 & GPT11 (one for each Cortex-M3 core)
      
      The MPU-side drivers will use this data to initialize the watchdog
      timers, and listen for any watchdog triggers. The BIOS-side code
      needs to configure and refresh these timers properly to not throw
      a watchdog error.
      
      These timers can be changed or removed as per the system integration
      needs, alongside appropriate equivalent changes on the firmware side.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      f1c4a33f
    • Suman Anna's avatar
      ARM: dts: omap5-uevm: Add system timers to DSP and IPU · f0954943
      Suman Anna authored
      The BIOS System Tick timers have been added for the IPU and DSP
      remoteproc devices for the OMAP5 uEVM boards. The following timers
      (same as the timers on OMAP4 Panda boards) are chosen:
              IPU : GPT3 (SMP-mode)
              DSP : GPT5
      
      IPU has two Cortex-M4 processors, and is currently expected to be
      running in SMP-mode, so only a single timer suffices to provide
      the BIOS tick timer. An additional timer should be added for the
      second processor in IPU if it were to be run in non-SMP mode. The
      timer value also needs to be unique from the ones used by other
      processors so that they can be run simultaneously.
      
      The timers are optional, but are mandatory to support device
      management features such as power management and watchdog support.
      The above are added to successfully boot and execute firmware images
      configured with the respective timers, images that use internal
      processor subsystem timers are not affected. The timers can be
      changed or removed as per the system integration needs, alongside
      equivalent changes on the firmware side.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      f0954943
    • Suman Anna's avatar
      ARM: dts: omap5-uevm: Add CMA pools and enable IPU & DSP · 1e48754f
      Suman Anna authored
      The CMA reserved memory nodes have been added for the IPU and DSP
      remoteproc devices on the OMAP5 uEVM board. These nodes are assigned
      to the respective rproc device nodes, and both the IPU and DSP remote
      processors are enabled for this board.
      
      The current CMA pools and sizes are defined statically for each device.
      The starting addresses are fixed to meet current dependencies on the
      remote processor firmwares, and will go away when the remote-side
      code has been improved to gather this information runtime during
      its initialization.
      
      An associated pair of the rproc node and its CMA node can be disabled
      later on if there is no use-case defined to use that remote processor.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      1e48754f
    • Suman Anna's avatar
      ARM: dts: omap5: Add aliases for rproc nodes · e8661220
      Suman Anna authored
      Add aliases for the DSP and IPU remoteproc processor
      nodes common to all OMAP5 boards. The aliases uses
      the stem "rproc", and are identical to the values
      chosen on OMAP4 boards.
      
      The aliases can be overridden, if needed, in the
      respective board files.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      e8661220
    • Suman Anna's avatar
      ARM: dts: omap5: Add DSP and IPU nodes · 3026ce47
      Suman Anna authored
      OMAP5, like OMAP4, also has two remote processor subsystems,
      DSP and IPU. The IPU subsystem though has dual Cortex-M4
      processors instead of the dual Cortex-M3 processors in OMAP4,
      but otherwise has almost the same set of features. Add the
      DT nodes for these two processor sub-systems for all OMAP5
      SoCs.
      
      The nodes have the 'iommus', 'clocks', 'resets', 'firmware' and
      'mboxes' properties added, and are disabled for now. The IPU node
      has its L2 RAM memory specified through the 'reg' and 'reg-names'
      properties. The DSP node doesn't have these since it doesn't have
      any L2 RAM memories, but has an additional 'ti,bootreg' property
      instead as it has a specific boot register that needs to be
      programmed for booting.
      
      These nodes should be enabled as per the individual product
      configuration in the corresponding board dts files.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      3026ce47
    • Suman Anna's avatar
      ARM: dts: omap4-panda-common:: Add system timers to DSP and IPU · 7f7d771c
      Suman Anna authored
      The BIOS System Tick timers have been added for the IPU and DSP
      remoteproc devices on all the OMAP4-based Panda boards. The
      following DMTimers are chosen:
      	IPU : GPT3 (SMP-mode)
      	DSP : GPT5
      
      IPU has two Cortex-M3 processors, and is currently expected to be
      running in SMP-mode, so only a single timer suffices to provide
      the BIOS tick timer. An additional timer should be added for the
      second processor in IPU if it were to be run in non-SMP mode. The
      timer value also needs to be unique from the ones used by other
      processors so that they can be run simultaneously.
      
      The timers are optional, but are mandatory to support device
      management features such as power management and watchdog support.
      The above are added to successfully boot and execute firmware images
      configured with the respective timers, images that use internal
      processor subsystem timers are not affected. The timers can be
      changed or removed as per the system integration needs, alongside
      equivalent changes on the firmware side.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      7f7d771c
    • Suman Anna's avatar
      ARM: dts: omap4-panda-common: Add CMA pools and enable IPU & DSP · b4778e78
      Suman Anna authored
      The CMA reserved memory nodes have been added for the IPU and DSP
      remoteproc devices on all the OMAP4-based Panda boards. These nodes
      are assigned to the respective rproc device nodes, and both the
      IPU and DSP remote processors are enabled for all these boards.
      
      The current CMA pools and sizes are defined statically for each device.
      The starting addresses are fixed to meet current dependencies on the
      remote processor firmwares, and will go away when the remote-side
      code has been improved to gather this information runtime during
      its initialization.
      
      An associated pair of the rproc node and its CMA node can be disabled
      later on if there is no use-case defined to use that remote processor.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      b4778e78
    • Suman Anna's avatar
      ARM: dts: omap4: Add aliases for rproc nodes · 691eb180
      Suman Anna authored
      Add aliases for the DSP and IPU remoteproc processor
      nodes common to all OMAP4 boards. The aliases uses
      the stem "rproc".
      
      The aliases can be overridden, if needed, in the
      respective board files.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      691eb180
    • Suman Anna's avatar
      ARM: dts: omap4: Add IPU DT node · 5ce170cd
      Suman Anna authored
      The DT node for the Dual-Cortex M3 IPU processor sub-system has
      been added for OMAP4 SoCs. The L2RAM memory region information
      has been added to the node through the 'reg' and 'reg-names'
      properties. The node has the 'iommus', 'clocks', 'resets',
      'mboxes' and 'firmware' properties also added, and is disabled
      for now. It should be enabled as per the individual product
      configuration in the corresponding board dts files.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      5ce170cd
    • Suman Anna's avatar
      ARM: dts: omap4: Update the DSP node · 9ae60ac1
      Suman Anna authored
      The compatible property for the DSP node is updated to match
      the OMAP remoteproc bindings. The node is moved from the soc
      node to the ocp node to better reflect the connectivity from
      MPU side.
      
      The node is updated with the 'ti,bootreg', 'clocks', 'resets',
      'iommus', 'mboxes' and 'firmware' properties. Note that the
      node does not have any 'reg' or 'reg-names' properties since
      it doesn't have any L2 RAM memory, but only Unicaches.
      
      The node is disabled for now, and should be enabled as per
      the individual product configuration in the corresponding
      board dts files.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      9ae60ac1
    • Suman Anna's avatar
      ARM: dts: omap5: Add timer_sys_ck clocks for timers · 52ddb6d9
      Suman Anna authored
      The commit d41e5304 ("clk: ti: omap5: cleanup unnecessary clock
      aliases") has cleaned up all timer_sys_ck clock aliases and retained
      only the timer_32k_ck clock alias. The OMAP clocksource timer driver
      though still uses this clock alias when reconfiguring the parent
      clock source for the timer functional clocks, so add these clocks
      to all the timer nodes except for the always-on timers 1 and 12.
      
      This is required by the OMAP remoteproc driver to successfully
      acquire a timer and configure the source clock to be driven from
      timer_sys_ck clock.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      52ddb6d9
    • Suman Anna's avatar
      ARM: dts: omap4: Add timer_sys_ck clocks for timers · 214ec031
      Suman Anna authored
      The commit 1c7de9f2 ("clk: ti: omap4: cleanup unnecessary clock
      aliases") has cleaned up all timer_sys_ck clock aliases and retained
      only the timer_32k_ck clock alias. The OMAP clocksource timer driver
      though still uses this clock alias when reconfiguring the parent
      clock source for the timer functional clocks, so add these clocks
      to all the timer nodes.
      
      This is required by the OMAP remoteproc driver to successfully
      acquire a timer and configure the source clock to be driven from
      timer_sys_ck clock.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      214ec031
    • Drew Fustini's avatar
      ARM: dts: am335x-pocketbeagle: set default mux for gpio pins · abe4e467
      Drew Fustini authored
      These pins on the PocketBeagle P1 and P2 headers are connected to AM3358
      balls with gpio lines, and these pins are not used for any other
      peripherals by default. These GPIO lines are unclaimed and could be used
      by userspace program through the gpiod ABI.
      
      This patch adds a "default" state in the am33xx_pinmux node and sets the
      mux for those pins to gpio (mode 7) and input enable.
      
      The "pinctrl-single,bias-pullup" and "pinctrl-single,bias-pulldown"
      pinconf properties are also set for each pin per the ball reset state in
      section 4.2 of the datasheet [0].
      
      This is the AM335x pin control register format in Table 9-60 [1]:
      
       bit     attribute      value
      ----------------------------------
      31-7     reserved       0 on reset
         6     slew           { 0: fast, 1: slow }
         5     rx_active      { 0: rx disable, 1: rx enabled }
         4     pu_typesel     { 0: pulldown select, 1: pullup select }
         3     puden          { 0: pud enable, 1: disabled }
         2     mode           3 bits to selec mode 0 to 7
         1     mode
         0     mode
      
      The values for the bias pinconf properties are derived as follows:
      
      pinctrl-single,bias-pullup   = <[input] [enabled] [disable] [mask]>;
      pinctrl-single,bias-pullup   = <  0x10      0x10      0x10   0x18 >;
      
                2^5    2^4    2^3    2^2    2^1    2^0  |
               0x20   0x10   0x08   0x04   0x02   0x01  |
      --------------------------------------------------|
      input       x      1      0     x      x      x   | 0x10
      enabled     x      1      0     x      x      x   | 0x10
      disabled    x      0      0     x      x      x   | 0x00
      mask        x      1      1     x      x      x   | 0x18
      
      pinctrl-single,bias-pulldown = <[input] [enabled] [disable] [mask]>;
      pinctrl-single,bias-pulldown = <   0x0       0x0      0x10   0x18 >;
      
                2^5    2^4    2^3    2^2    2^1    2^0  |
               0x20   0x10   0x08   0x04   0x02   0x01  |
      --------------------------------------------------|
      input       x      0      0     x      x      x   | 0x00
      enabled     x      0      0     x      x      x   | 0x00
      disabled    x      1      0     x      x      x   | 0x10
      mask        x      1      1     x      x      x   | 0x18
      
      [0] http://www.ti.com/lit/ds/symlink/am3358.pdf
      [1] https://www.ti.com/lit/ug/spruh73q/spruh73q.pdfSigned-off-by: default avatarDrew Fustini <drew@beagleboard.org>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      abe4e467
    • Tony Lindgren's avatar
      ARM: OMAP2+: Drop legacy platform data for am4 dwc3 · 3c881456
      Tony Lindgren authored
      We can now probe devices with ti-sysc interconnect driver and dts
      data. Let's drop the related platform data and custom ti,hwmods
      dts property.
      
      As we're just dropping data, and the early platform data init
      is based on the custom ti,hwmods property, we want to drop both
      the platform data and ti,hwmods property in a single patch.
      
      [tony@atomide.com: fixed typo for am3 vs am4]
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      3c881456
    • Tony Lindgren's avatar
      bus: ti-sysc: Add missing quirk flags for usb_host_hs · 4254632d
      Tony Lindgren authored
      Similar to what we have for the legacy platform data, we need to
      configure SWSUP_SIDLE and SWSUP_MSTANDBY quirks for usb_host_hs.
      
      These are needed to drop the legacy platform data for usb_host_hs.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      4254632d
    • Arnd Bergmann's avatar
      Merge tag 'arm-soc/for-5.9/devicetree' of https://github.com/Broadcom/stblinux into arm/dt · 42027dfe
      Arnd Bergmann authored
      This pull request contains Broadcom ARM-based SoCs Device Tree changes
      for 5.9 please pull the following:
      
      - Rafal specifies the switch ports for various Luxul devices (XAP-1410,
        XAP-1510, XAP-1610, XWC-1000, XWC-2000, XWR-1200, XWR-3100, XWR-3150)
      
      - Krzysztof fixes the L2 cache controller node name to conform to
        dtschema
      
      - Maxime introduces two new clock providers for Raspberry Pi 4, one to
        support firmware based clocks and another one for the DVP block
        feeding into the two HDMI blocks.
      
      * tag 'arm-soc/for-5.9/devicetree' of https://github.com/Broadcom/stblinux:
        ARM: dts: bcm: Align L2 cache-controller nodename with dtschema
        ARM: dts: BCM5301X: Specify switch ports for Luxul devices
        ARM: dts: bcm2711: Add HDMI DVP
        ARM: dts: bcm2711: Add firmware clocks node
      
      Link: https://lore.kernel.org/r/20200707045759.17562-1-f.fainelli@gmail.comSigned-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      42027dfe
    • Arnd Bergmann's avatar
      Merge tag 'omap-for-v5.9/dt-signed' of... · 67b25638
      Arnd Bergmann authored
      Merge tag 'omap-for-v5.9/dt-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into arm/dt
      
      Device tree changes for omaps for v5.9 merge window
      
      This series of changes configures the GPIO line names for am335x beaglebone
      black and pocketbeagle to make it easier to configure the pins. To make use
      of the pins, we also add the gpio-ranges for am335x.
      
      We also enable IPU and DSP repmoteproc for am5729-beaglebone-ai, and then
      there are two non-urgent dtschema validator warning fixes.
      
      * tag 'omap-for-v5.9/dt-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
        ARM: dts: am335x-pocketbeagle: add gpio-line-names
        ARM: dts: am335x-boneblack: add gpio-line-names
        ARM: dts: am33xx-l4: add gpio-ranges
        ARM: dts: am5729-beaglebone-ai: Disable ununsed mailboxes
        ARM: dts: am5729-beaglebone-ai: Enable IPU & DSP rprocs
        ARM: dts: am: Align L2 cache-controller nodename with dtschema
        ARM: dts: omap: Align L2 cache-controller nodename with dtschema
      
      Link: https://lore.kernel.org/r/pull-1594402929-762188@atomide.comSigned-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      67b25638
    • Arnd Bergmann's avatar
      Merge tag 'uniphier-dt64-v5.9' of... · dfe2a4cf
      Arnd Bergmann authored
      Merge tag 'uniphier-dt64-v5.9' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier into arm/dt
      
      UniPhier ARM64 SoC DT updates for v5.9
      
      - add missing interrupts property to support card serial
      
      - fix node names to follow the DT schema
      
      - add clock-names and reset-names to pcie-phy
      
      * tag 'uniphier-dt64-v5.9' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier:
        arm64: dts: uniphier: Add missing clock-names and reset-names to pcie-phy
        arm64: dts: uniphier: Rename ethphy node to ethernet-phy
        arm64: dts: uniphier: give fixed port number to support card serial
        arm64: dts: uniphier: add interrupts to support card serial
      
      Link: https://lore.kernel.org/r/CAK7LNARK4SKhSW-xwgc3vq7FO7N864jPgzm8NtsGOv8wVFVyBQ@mail.gmail.comSigned-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      dfe2a4cf
    • Arnd Bergmann's avatar
      Merge tag 'uniphier-dt-v5.9' of... · 056a7ecf
      Arnd Bergmann authored
      Merge tag 'uniphier-dt-v5.9' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier into arm/dt
      
      UniPhier ARM SoC DT updates for v5.9
      
      - add missing interrupts property to support card serial
      
      - fix node names to follow the DT schema
      
      - add PCIe endpoint and PHY nodes for Pro5 SoC
      
      - simplify device hierarchy of support-card.dtsi
      
      * tag 'uniphier-dt-v5.9' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier:
        ARM: dts: uniphier: simplify support-card node structure
        ARM: dts: uniphier: Add PCIe endpoint and PHY node for Pro5
        ARM: dts: uniphier: Rename ethphy node to ethernet-phy
        ARM: dts: uniphier: give fixed port number to support card serial
        ARM: dts: uniphier: rename support card serial node to fix schema warning
        ARM: dts: uniphier: add interrupts to support card serial
      
      Link: https://lore.kernel.org/r/CAK7LNARGDcCKxV3-H7WmuZAVe49n0QF+672-KN0tsP0och0a_A@mail.gmail.comSigned-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      056a7ecf
  4. 10 Jul, 2020 5 commits
  5. 07 Jul, 2020 8 commits