1. 15 6月, 2019 1 次提交
    • A
      ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ipg" clock to SDMA · 584cabc6
      Andrey Smirnov 提交于
      [ Upstream commit 8979117765c19edc3b01cc0ef853537bf93eea4b ]
      
      Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb"
      clock to determine if it needs to configure the IP block as operating
      at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both
      clocks as IMX6SX_CLK_SDMA results in driver incorrectly thinking that
      ratio is 1:1 which results in broken SDMA funtionality. Fix the code
      to specify IMX6SX_CLK_IPG as "ipg" clock for SDMA, to avoid detecting
      incorrect clock ratio.
      Signed-off-by: NAndrey Smirnov <andrew.smirnov@gmail.com>
      Cc: Angus Ainslie (Purism) <angus@akkea.ca>
      Cc: Chris Healy <cphealy@gmail.com>
      Cc: Lucas Stach <l.stach@pengutronix.de>
      Cc: Fabio Estevam <fabio.estevam@nxp.com>
      Cc: Shawn Guo <shawnguo@kernel.org>
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: NShawn Guo <shawnguo@kernel.org>
      Signed-off-by: NSasha Levin <sashal@kernel.org>
      584cabc6
  2. 14 3月, 2019 1 次提交
  3. 11 7月, 2018 2 次提交
  4. 03 7月, 2018 1 次提交
  5. 28 6月, 2018 1 次提交
  6. 19 6月, 2018 1 次提交
  7. 20 5月, 2018 1 次提交
    • F
      ARM: dts: imx6/7: Remove unit-address from anatop regulators · 71db3948
      Fabio Estevam 提交于
      Remove unit-address and reg property from anatop regulators to fix
      the following DTC warnings with W=1:
      
      arch/arm/boot/dts/imx6dl-apf6dev.dtb: Warning (unique_unit_address): /soc/aips-bus@2000000/anatop@20c8000/regulator-vddcore@20c8140: duplicate unit-address (also used in node /soc/aips-bus@2000000/anatop@20c8000/regulator-vddpu@20c8140)
      arch/arm/boot/dts/imx6dl-apf6dev.dtb: Warning (unique_unit_address): /soc/aips-bus@2000000/anatop@20c8000/regulator-vddcore@20c8140: duplicate unit-address (also used in node /soc/aips-bus@2000000/anatop@20c8000/regulator-vddsoc@20c8140)
      arch/arm/boot/dts/imx6dl-apf6dev.dtb: Warning (unique_unit_address): /soc/aips-bus@2000000/anatop@20c8000/regulator-vddpu@20c8140: duplicate unit-address (also used in node /soc/aips-bus@2000000/anatop@20c8000/regulator-vddsoc@20c8140)
      Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
      Signed-off-by: NShawn Guo <shawnguo@kernel.org>
      71db3948
  8. 14 5月, 2018 1 次提交
  9. 02 5月, 2018 1 次提交
  10. 24 2月, 2018 1 次提交
  11. 12 2月, 2018 3 次提交
  12. 26 12月, 2017 7 次提交
  13. 23 10月, 2017 1 次提交
  14. 20 10月, 2017 1 次提交
  15. 16 7月, 2017 1 次提交
  16. 21 5月, 2017 1 次提交
  17. 10 4月, 2017 2 次提交
  18. 24 1月, 2017 1 次提交
  19. 03 1月, 2017 1 次提交
    • F
      ARM: dts: imx6: Disable "weim" node in the dtsi files · 116dad7d
      Fabio Estevam 提交于
      Commit 1be81ea5 ("ARM: dts: imx6: Add imx-weim parameters to
      dtsi's") causes the following probe error when the weim node is not
      present on the board dts (such as imx6q-sabresd):
      
      imx-weim 21b8000.weim: Invalid 'ranges' configuration
      imx-weim: probe of 21b8000.weim failed with error -22
      
      There is no need to always enable the "weim" node on mx6. Do the same
      as in the other i.MX dtsi files where "weim" is disabled and only gets
      enabled on a per dts basis.
      
      All the imx6 weim dts users explicitily provide 'status = "okay"', so
      this change has no impact on current imx6 weim users.
      
      If a board does not use the weim driver it will not describe its 'ranges'
      property, so simply disable the 'weim' node in the imx6 dtsi files to
      avoid such probe error message.
      
      Fixes: 1be81ea5 ("ARM: dts: imx6: Add imx-weim parameters to dtsi's")
      Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
      Signed-off-by: NShawn Guo <shawnguo@kernel.org>
      116dad7d
  20. 14 11月, 2016 1 次提交
  21. 05 11月, 2016 1 次提交
  22. 02 11月, 2016 1 次提交
  23. 24 10月, 2016 1 次提交
    • M
      ARM: dts: imx6sx: Fix LCDIF interrupt type · f7f3b484
      Marek Vasut 提交于
      The LCDIF interrupt should be triggered by the rising edge of the
      IRQ line because we only want the interrupt to trigger once per each
      frame. It seems the LCDIF IRQ line cannot be explicitly de-asserted
      by software, so the previous behavior before this patch, where the
      interrupt was triggered by level-high status of the IRQ line, caused
      the interrupt to fire again immediatelly after it was handled, which
      caused the system to lock up due to the high rate of interrupts.
      Signed-off-by: NMarek Vasut <marex@denx.de>
      Cc: Lucas Stach <l.stach@pengutronix.de>
      Cc: Fabio Estevam <fabio.estevam@nxp.com>
      Signed-off-by: NShawn Guo <shawnguo@kernel.org>
      f7f3b484
  24. 09 9月, 2016 1 次提交
  25. 29 8月, 2016 1 次提交
  26. 06 6月, 2016 1 次提交
  27. 26 4月, 2016 1 次提交
  28. 13 4月, 2016 2 次提交
  29. 22 12月, 2015 1 次提交