1. 06 Apr, 2021 1 commit
  2. 04 Oct, 2020 3 commits
  3. 10 Jul, 2020 2 commits
  4. 19 Jun, 2020 2 commits
  5. 06 Jun, 2020 1 commit
  6. 11 Dec, 2019 2 commits
    • Marek Behún's avatar
      drivers: marvell: comphy-a3700: support SGMII COMPHY power off · 629dd61f
      Marek Behún authored
      
      
      Add support for powering off the SGMII COMPHY (on lanes 0 and 1).
      This is needed sometimes on Turris Mox when using KEXEC.
      
      There is also another benefit of a little energy saving when the given
      network interface is down.
      Signed-off-by: default avatarMarek Behún <marek.behun@nic.cz>
      Change-Id: I55ae0fe3627e7cc0f65c78a00771939d8bf5399f
      629dd61f
    • Marek Behún's avatar
      drivers: marvell: comphy-a3700: fix USB3 powering on when on lane 2 · b662232d
      Marek Behún authored
      
      
      When USB3 is on lane 2 and indirect register access is used, the polling
      at the end of the mvebu_a3700_comphy_usb3_power_on function is
      incorrect.
      
      The LOOPBACK_REG0 register should not be used at all. Instead we have to
      write the LANE_STATUS1 register address (with offset
      USB3PHY_LANE2_REG_BASE_OFFSET) into the indirect address register and
      then we should poll indirect data register.
      
      This fixes problems on Turris Mox, which uses lane 2 for USB3.
      Signed-off-by: default avatarMarek Behún <marek.behun@nic.cz>
      Change-Id: I968b0cccee5ddbe10a2b5614e52e52d87682aacd
      b662232d
  7. 04 Jan, 2019 1 commit
    • Antonio Nino Diaz's avatar
      Sanitise includes across codebase · 09d40e0e
      Antonio Nino Diaz authored
      Enforce full include path for includes. Deprecate old paths.
      
      The following folders inside include/lib have been left unchanged:
      
      - include/lib/cpus/${ARCH}
      - include/lib/el3_runtime/${ARCH}
      
      The reason for this change is that having a global namespace for
      includes isn't a good idea. It defeats one of the advantages of having
      folders and it introduces problems that are sometimes subtle (because
      you may not know the header you are actually including if there are two
      of them).
      
      For example, this patch had to be created because two headers were
      called the same way: e0ea0928 ("Fix gpio includes of mt8173 platform
      to avoid collision."). More recently, this patch has had similar
      problems: 46f9b2c3 ("drivers: add tzc380 support").
      
      This problem was introduced in commit 4ecca339
      
       ("Move include and
      source files to logical locations"). At that time, there weren't too
      many headers so it wasn't a real issue. However, time has shown that
      this creates problems.
      
      Platforms that want to preserve the way they include headers may add the
      removed paths to PLAT_INCLUDES, but this is discouraged.
      
      Change-Id: I39dc53ed98f9e297a5966e723d1936d6ccf2fc8f
      Signed-off-by: default avatarAntonio Nino Diaz <antonio.ninodiaz@arm.com>
      09d40e0e
  8. 04 Dec, 2018 2 commits
  9. 08 Nov, 2018 1 commit
    • Antonio Nino Diaz's avatar
      Standardise header guards across codebase · c3cf06f1
      Antonio Nino Diaz authored
      
      
      All identifiers, regardless of use, that start with two underscores are
      reserved. This means they can't be used in header guards.
      
      The style that this project is now to use the full name of the file in
      capital letters followed by 'H'. For example, for a file called
      "uart_example.h", the header guard is UART_EXAMPLE_H.
      
      The exceptions are files that are imported from other projects:
      
      - CryptoCell driver
      - dt-bindings folders
      - zlib headers
      
      Change-Id: I50561bf6c88b491ec440d0c8385c74650f3c106e
      Signed-off-by: default avatarAntonio Nino Diaz <antonio.ninodiaz@arm.com>
      c3cf06f1
  10. 22 Oct, 2018 1 commit
  11. 18 Oct, 2018 1 commit
    • Grzegorz Jaszczyk's avatar
      mvebu: cp110: introduce COMPHY porting layer · 42a29337
      Grzegorz Jaszczyk authored
      
      
      Some of COMPHY parameters depends on the hw connection between the SoC
      and the PHY, which can vary on different boards e.g. due to different
      wires length. Define the "porting layer" with some defaults
      parameters. It ease updating static values which needs to be updated due
      to board differences, which are now grouped in one place.
      
      Example porting layer for a8k-db is under:
      plat/marvell/a8k/a80x0/board/phy-porting-layer.h
      
      If for some boards parameters are not defined (missing
      phy-porting-layer.h), the default values are used
      (drivers/marvell/comphy/phy-default-porting-layer.h)
      and the following compilation warning is show:
      "Using default comphy params - you may need to suit them to your board".
      
      The common COMPHY driver code is extracted in order to be shared with
      future COMPHY driver for A3700 SoC platforms
      Signed-off-by: default avatarGrzegorz Jaszczyk <jaz@semihalf.com>
      Signed-off-by: default avatarIgal Liberman <igall@marvell.com>
      Signed-off-by: default avatarKonstantin Porotchkin <kostap@marvell.com>
      42a29337
  12. 02 Sep, 2018 2 commits
  13. 22 Aug, 2018 1 commit
  14. 10 Aug, 2018 1 commit
  15. 18 Jul, 2018 1 commit