1. 06 6月, 2019 3 次提交
  2. 10 4月, 2019 1 次提交
  3. 18 3月, 2019 2 次提交
  4. 25 2月, 2019 1 次提交
  5. 08 2月, 2019 1 次提交
  6. 31 1月, 2019 1 次提交
  7. 23 1月, 2019 3 次提交
  8. 26 11月, 2018 2 次提交
  9. 23 11月, 2018 2 次提交
  10. 19 11月, 2018 1 次提交
  11. 08 11月, 2018 2 次提交
  12. 05 11月, 2018 8 次提交
  13. 26 9月, 2018 1 次提交
  14. 25 9月, 2018 1 次提交
    • Y
      arm64: dts: renesas: revise properties for R-Car Gen3 SoCs' usb 2.0 · 737e05bf
      Yoshihiro Shimoda 提交于
      R-Car Gen3 SoCs need to enable/deassert clocks/resets of both usb 2.0
      host (included phy) and peripheral. Otherwise, other side device
      cannot work correctly. So, this patch revises properties of clocks
      and resets. After that, each device driver can enable/deassert
      clocks/resets by its self.
      
      Notes:
       - To work the renesas_usbhs driver correctly when host side drivers
         are disabled and the renesas_usbhs driver doesn't have multiple
         clock management, this patch doesn't change the order of the clocks
         property in each hsusb node.
       - This patch doesn't have any side-effects even if the renesas_usbhs
         driver doesn't have reset_control and multiple clock management.
      Signed-off-by: NYoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      737e05bf
  15. 19 9月, 2018 1 次提交
  16. 13 9月, 2018 6 次提交
  17. 11 9月, 2018 1 次提交
  18. 27 8月, 2018 1 次提交
  19. 20 7月, 2018 1 次提交
  20. 16 7月, 2018 1 次提交
    • M
      arm64: dts: renesas: r8a779{65,80,90}: Add IPMMU devices nodes · 55697cbb
      Magnus Damm 提交于
      Add IPMMU device nodes for the R-Car M3-N (r8a77965),
      V3H (r8a77980) and E3 (r8a77990) SoCs.
      
      * The r8a77965 IPMMU is quite similar to r8a7796 however VP0
        has been added and PV1 has been removed. Also the IMSSTR
        bit assignment has been reworked.
      
      * The r8a77980 IPMMU is quite similar to r8a77970 however VC0
        has been added. The IMSSTR bit assignment has also been
        reworked. Power domains are also quite different however the
        the documentation is rather unclear about this topic.
      
        Until we know better VC0 gets assigned to R8A77980_PD_ALWAYS_ON.
      
      * The r8a77990 IPMMU is similar to r8a77995. Power domains are
        however different and the public documentation is still unclear.
      
        Based on preliminary information from the hardware team the R-Car E3
        SoC comes with an IPMMU-VP0 device in an Always-on power domain and
        the IPMMU-VC0 is placed as expected in the A3VC power domain.
      Signed-off-by: NMagnus Damm <damm+renesas@opensource.se>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      55697cbb