1. 16 3月, 2019 1 次提交
  2. 15 3月, 2019 1 次提交
  3. 13 3月, 2019 4 次提交
  4. 11 3月, 2019 3 次提交
  5. 10 3月, 2019 4 次提交
    • M
      ARM: socfpga: Disable D cache in SPL · 7544ad03
      Marek Vasut 提交于
      The bootrom seems to leave the D-cache in messed up state, make sure
      the SPL disables it so it can not interfere with operation.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Cc: Chin Liang See <chin.liang.see@intel.com>
      Cc: Dinh Nguyen <dinguyen@kernel.org>
      Cc: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
      Cc: Tien Fong Chee <tien.fong.chee@intel.com>
      7544ad03
    • D
      ARM: socfpga: fix data and tag latency values for pl310 cache controller · 532a54e6
      Dinh Nguyen 提交于
      The values for the data and tag latency settings on the PL310 caches
      controller is an (n-1). For example, the "arm,tag-latency" is specified
      as <1 1 1>, so the values that should be written to register should be
      0x000. And for the "arm,data-latency" specified as <2 1 1>, the register
      value should be 0x010.
      Signed-off-by: NDinh Nguyen <dinguyen@kernel.org>
      532a54e6
    • E
      ARM: dts: rmobile: Zap redundant USB/SDHI nodes on M3N · 3a4511ce
      Eugeniu Rosca 提交于
      v2019.01 commit cbff9f80 ("ARM: dts: rmobile: Sync Gen3 DTs with
      Linux 4.19.6") made the sdhi/usb nodes available in r8a77965.dtsi.
      
      Hence, remove the SDHI/USB nodes from r8a77965-u-boot.dtsi. This is
      equivalent to partially reverting below v2019.01 commits:
       - f529bc55 ("ARM: dts: rmobile: Extract USB nodes on M3N")
       - 830b94f7 ("ARM: dts: rmobile: Extract SDHI nodes on M3N")
      
      Duplicating the nodes from <soc>.dtsi to <soc>-u-boot.dtsi is obviously:
       - not needed if no U-boot-specific changes are needed in those nodes.
       - potentially dangerous/error-prone, since the duplicated properties
         override the properties originally defined in <soc>.dtsi. One
         possible consequence is that <soc>.dtsi is getting an update from
         Linux, while <soc>-u-boot.dtsi stays unchanged. In this situation,
         the obsolete property values from <soc>-u-boot.dtsi will take
         precedence masking some of the <soc>.dtsi updates, potentially
         leading to all kind of obscure issues.
      
      Below is the dtdiff of r8a77965-salvator-x-u-boot.dtb (the only "user"
      of r8a77965-u-boot.dtsi) before and after the patch (slightly
      reformatted to avoid 'git am/apply' issues and to reduce the width).
      
      What below output means is there is already a mismatch in some of
      SDHI/USB nodes between r8a77965.dtsi and r8a77965-u-boot.dtsi. Since no
      U-Boot customization is needed in SDHI/USB DT nodes, get rid of them in
      r8a77965-u-boot.dtsi.
      
      $> dtdiff before-r8a77965-salvator-x-u-boot.dtb \
                 after-r8a77965-salvator-x-u-boot.dtb
       --- /dev/fd/63  2019-03-09 12:57:40.877963983 +0100
       +++ /dev/fd/62  2019-03-09 12:57:40.877963983 +0100
       @@ -1471,7 +1471,7 @@
              bus-width = <0x4>;
              cd-gpios = <0x51 0xc 0x1>;
              clocks = <0x6 0x1 0x13a>;
       -      compatible = "renesas,sdhi-r8a77965";
       +      compatible = "renesas,sdhi-r8a77965", "renesas,rcar-gen3-sdhi";
              interrupts = <0x0 0xa5 0x4>;
              max-frequency = <0xc65d400>;
              pinctrl-0 = <0x4d>;
       @@ -1492,7 +1492,7 @@
      
            sd@ee120000 {
              clocks = <0x6 0x1 0x139>;
       -      compatible = "renesas,sdhi-r8a77965";
       +      compatible = "renesas,sdhi-r8a77965", "renesas,rcar-gen3-sdhi";
              interrupts = <0x0 0xa6 0x4>;
              max-frequency = <0xbebc200>;
              power-domains = <0x1 0x20>;
       @@ -1504,7 +1504,7 @@
            sd@ee140000 {
              bus-width = <0x8>;
              clocks = <0x6 0x1 0x138>;
       -      compatible = "renesas,sdhi-r8a77965";
       +      compatible = "renesas,sdhi-r8a77965", "renesas,rcar-gen3-sdhi";
              fixed-emmc-driver-type = <0x1>;
              interrupts = <0x0 0xa7 0x4>;
              max-frequency = <0xbebc200>;
       @@ -1526,7 +1526,7 @@
              bus-width = <0x4>;
              cd-gpios = <0x5a 0xf 0x1>;
              clocks = <0x6 0x1 0x137>;
       -      compatible = "renesas,sdhi-r8a77965";
       +      compatible = "renesas,sdhi-r8a77965", "renesas,rcar-gen3-sdhi";
              interrupts = <0x0 0xa8 0x4>;
              max-frequency = <0xc65d400>;
              pinctrl-0 = <0x56>;
       @@ -1868,14 +1868,14 @@
      
            usb-phy@ee0a0200 {
              #phy-cells = <0x0>;
       -      clocks = <0x6 0x1 0x2be>;
       +      clocks = <0x6 0x1 0x2bf>;
              compatible = "renesas,usb2-phy-r8a77965", "renesas,rcar-gen3-usb2-phy";
              phandle = <0x47>;
              pinctrl-0 = <0x4c>;
              pinctrl-names = "default";
              power-domains = <0x1 0x20>;
              reg = <0x0 0xee0a0200 0x0 0x700>;
       -      resets = <0x6 0x2be>;
       +      resets = <0x6 0x2bf>;
              status = "okay";
            };
      Signed-off-by: NEugeniu Rosca <erosca@de.adit-jv.com>
      3a4511ce
    • M
      ARM: dts: rmobile: Force 1-bit bus width on Gen2 QSPI · fc3ed156
      Marek Vasut 提交于
      U-Boot currently uses Gen2 QSPI in 1-bit mode, enforce it until
      we can do better using the new SPI NOR framework.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      fc3ed156
  6. 04 3月, 2019 2 次提交
  7. 03 3月, 2019 1 次提交
  8. 01 3月, 2019 1 次提交
  9. 25 2月, 2019 6 次提交
    • M
      ARM: rmobile: Imply SoC per board · 30b62ca0
      Marek Vasut 提交于
      Imply all SoCs supported by a given board. This allows building single
      U-Boot binary for boards which can have multiple SoCs.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      30b62ca0
    • M
      ARM: rmobile: Imply pinctrl drivers per SoC · 669367f6
      Marek Vasut 提交于
      Imply preferred pin control driver per SoC, no functional change.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      669367f6
    • M
      ARM: rmobile: Imply clock drivers per SoC · 46467cea
      Marek Vasut 提交于
      Imply preferred clock driver per SoC, no functional change.
      Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      46467cea
    • M
      ARM: socfpga: Clear PL310 early in SPL · 4a9743f7
      Marek Vasut 提交于
      On SoCFPGA Gen5 systems, it can rarely happen that a reboot from Linux
      will result in stale data in PL310 L2 cache controller. Even if the L2
      cache controller is disabled via the CTRL register CTRL_EN bit, those
      data can interfere with operation of devices using DMA, like e.g. the
      DWMMC controller. This can in turn cause e.g. SPL to fail reading data
      from SD/MMC.
      
      The obvious solution here would be to fully reset the L2 cache controller
      via the reset manager MPUMODRST L2 bit, however this causes bus hang even
      if executed entirely from L1 I-cache to avoid generating any bus traffic
      through the L2 cache controller.
      
      This patch thus configures and enables the L2 cache controller very early
      in the SPL boot process, clears the L2 cache and disables the L2 cache
      controller again.
      
      The reason for doing it in SPL is because we need to avoid accessing any
      of the potentially stale data in the L2 cache, and we are certain any of
      the stale data will be below the OCRAM address range. To further reduce
      bus traffic during the L2 cache invalidation, we enable L1 I-cache and
      run the invalidation code entirely out of the L1 I-cache.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Cc: Dalon Westergreen <dwesterg@gmail.com>
      Cc: Dinh Nguyen <dinguyen@kernel.org>
      4a9743f7
    • M
      ARM: socfpga: Configure PL310 latencies · 2c0b300b
      Marek Vasut 提交于
      Configure the PL310 tag and data latency registers, which slightly
      improves performance and aligns the behavior with Linux.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Cc: Dalon Westergreen <dwesterg@gmail.com>
      Cc: Dinh Nguyen <dinguyen@kernel.org>
      2c0b300b
    • M
      ARM: cache: Fix incorrect bitwise operation · b275c9ab
      Marek Vasut 提交于
      The loop implemented in the code is supposed to check whether the
      PL310 operation register has any bit from the mask set. Currently,
      the code checks whether the PL310 operation register has any bit
      set AND whether the mask is non-zero, which is incorrect. Fix the
      conditional.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Cc: Dalon Westergreen <dwesterg@gmail.com>
      Cc: Dinh Nguyen <dinguyen@kernel.org>
      Cc: Tom Rini <trini@konsulko.com>
      Fixes: 93bc2193 ("armv7: add PL310 support to u-boot")
      b275c9ab
  10. 21 2月, 2019 2 次提交
  11. 20 2月, 2019 4 次提交
  12. 19 2月, 2019 11 次提交