1. 03 6月, 2015 1 次提交
  2. 05 1月, 2015 3 次提交
  3. 18 7月, 2014 1 次提交
    • M
      ARM: dts: imx: remove ssi fsl,mode for audio cards · 9eb0e5f9
      Markus Pargmann 提交于
      The DAI mode is and should be configured by the sound card driver as
      codec and ssi have to be in the right modes to communicate with each
      other. It is possible to operate the ssi unit or the codec in master mode,
      sometimes even on the same board in different configurations.
      
      With the latest changes in the fsl-ssi driver, the 'fsl,mode' property
      is only handled as a fallback property. If the sound card sets the DAI
      mode correctly, this fallback configuration is dropped.
      Signed-off-by: NMarkus Pargmann <mpa@pengutronix.de>
      Signed-off-by: NShawn Guo <shawn.guo@freescale.com>
      9eb0e5f9
  4. 16 5月, 2014 1 次提交
  5. 10 2月, 2014 1 次提交
    • T
      ARM: dts: imx6qdl-sabrelite: use GPIO_6 for FEC interrupt. · 6261c4c8
      Troy Kisky 提交于
      This works around a hardware bug.
      From "Chip Errata for the i.MX 6Dual/6Quad"
      
      ERR006687 ENET: Only the ENET wake-up interrupt request can wake the
      system from Wait mode.
      
      The ENET block generates many interrupts. Only one of these interrupt lines
      is connected to the General Power Controller (GPC) block, but a logical OR
      of all of the ENET interrupts is connected to the General Interrupt Controller
      (GIC). When the system enters Wait mode, a normal RX Done or TX Done does not
      wake up the system because the GPC cannot see this interrupt. This impacts
      performance of the ENET block because its interrupts are serviced only when
      the chip exits Wait mode due to an interrupt from some other wake-up source.
      
      Before this patch, ping times of a Sabre Lite board are quite
      random:
      ping 192.168.0.13 -i.5 -c5
      PING 192.168.0.13 (192.168.0.13) 56(84) bytes of data.
      64 bytes from 192.168.0.13: icmp_req=1 ttl=64 time=15.7 ms
      64 bytes from 192.168.0.13: icmp_req=2 ttl=64 time=14.4 ms
      64 bytes from 192.168.0.13: icmp_req=3 ttl=64 time=13.4 ms
      64 bytes from 192.168.0.13: icmp_req=4 ttl=64 time=12.4 ms
      64 bytes from 192.168.0.13: icmp_req=5 ttl=64 time=11.4 ms
      
      === 192.168.0.13 ping statistics ===
      5 packets transmitted, 5 received, 0% packet loss, time 2004ms
      rtt min/avg/max/mdev = 11.431/13.501/15.746/1.508 ms
      ____________________________________________________
      After this patch:
      
      ping 192.168.0.13 -i.5 -c5
      PING 192.168.0.13 (192.168.0.13) 56(84) bytes of data.
      64 bytes from 192.168.0.13: icmp_req=1 ttl=64 time=0.120 ms
      64 bytes from 192.168.0.13: icmp_req=2 ttl=64 time=0.175 ms
      64 bytes from 192.168.0.13: icmp_req=3 ttl=64 time=0.169 ms
      64 bytes from 192.168.0.13: icmp_req=4 ttl=64 time=0.168 ms
      64 bytes from 192.168.0.13: icmp_req=5 ttl=64 time=0.172 ms
      
      === 192.168.0.13 ping statistics ===
      5 packets transmitted, 5 received, 0% packet loss, time 1999ms
      rtt min/avg/max/mdev = 0.120/0.160/0.175/0.026 ms
      ____________________________________________________
      
      Also, apply same change to imx6qdl-nitrogen6x.
      
      This change may not be appropriate for all boards.
      Sabre Lite uses GPIO6 as a power down output for a ov5642
      camera. As this expansion board does not yet work with mainline,
      this is not yet a conflict. It would be nice to have an alternative
      fix for boards where this is a problem.
      
      For example Sabre SD uses GPIO6 for I2C3_SDA. It also
      has long ping times currently. But cannot use this fix
      without giving up a touchscreen.
      
      Its ping times are also random.
      
      ping 192.168.0.19 -i.5 -c5
      PING 192.168.0.19 (192.168.0.19) 56(84) bytes of data.
      64 bytes from 192.168.0.19: icmp_req=1 ttl=64 time=16.0 ms
      64 bytes from 192.168.0.19: icmp_req=2 ttl=64 time=15.4 ms
      64 bytes from 192.168.0.19: icmp_req=3 ttl=64 time=14.4 ms
      64 bytes from 192.168.0.19: icmp_req=4 ttl=64 time=13.4 ms
      64 bytes from 192.168.0.19: icmp_req=5 ttl=64 time=12.4 ms
      
      === 192.168.0.19 ping statistics ---
      5 packets transmitted, 5 received, 0% packet loss, time 2003ms
      rtt min/avg/max/mdev = 12.451/14.369/16.057/1.316 ms
      Signed-off-by: NTroy Kisky <troy.kisky@boundarydevices.com>
      CC: Ranjani Vaidyanathan <ra5478@freescale.com>
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      6261c4c8
  6. 09 2月, 2014 21 次提交
  7. 29 9月, 2013 1 次提交
  8. 26 9月, 2013 2 次提交
  9. 22 8月, 2013 3 次提交
    • S
      ARM: imx6q: remove board specific CLKO setup · a94f8ecb
      Shawn Guo 提交于
      The CLKO is widely used by imx6q board designs to clock audio codec.
      Since most codecs accept 24 MHz frequency, let's initially set up CLKO
      with OSC24M (cko <-- cko2 <-- osc).  Then those board specific CLKO
      setup for audio codec can be removed.
      
      The board dts files also need an update on cko reference in codec node.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      a94f8ecb
    • R
      ARM: dtsi: enable ahci sata on imx6q platforms · 0fb1f804
      Richard Zhu 提交于
      Only imx6q has the ahci sata controller, enable
      it on imx6q platforms.
      Signed-off-by: NRichard Zhu <r65037@freescale.com>
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      0fb1f804
    • S
      ARM: dts: imx: share pad macro names between imx6q and imx6dl · c56009b2
      Shawn Guo 提交于
      The imx6q and imx6dl are two pin-to-pin compatible SoCs.  The same board
      design can work with either chip plugged into the socket, e.g. sabresd
      and sabreauto boards.
      
      We currently define pin groups in imx6q.dtsi and imx6dl.dtsi
      respectively because the pad macro names are different between two
      chips.  This brings a maintenance burden on having the same label point
      to the same pin group defined in two places.
      
      The patch replaces prefix MX6Q_ and MX6DL_ with MX6QDL_ for both SoCs
      pad macro names.  Then the pin groups becomes completely common between
      imx6q and imx6dl and can just be moved into imx6qdl.dtsi, so that the
      long term maintenance of imx6q/dt pin settings becomes easier.
      
      Unfortunately, the change brings some dramatic diff stat, but it's all
      about DTS file, and the ultimate net diff stat is good.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      c56009b2
  10. 09 4月, 2013 2 次提交
    • S
      pinctrl: imx: move hard-coding data into device tree · e1641531
      Shawn Guo 提交于
      Currently, all imx pinctrl drivers maintain a big array of struct
      imx_pin_reg which hard-codes data like register offset and mux mode
      setting for each pin function.  Every time a new imx SoC support is
      added, we need to add such a big mount of data.  With moving to single
      kernel build, it's only matter of time to be blamed on memory consuming.
      
      With DTC pre-processor support in place, the patch moves all these data
      into device tree by redefining the PIN_FUNC_ID in imxXX-pinfunc.h and
      changing the PIN_FUNC_ID parsing code a little bit.
      
      The pin id gets re-numbered based on mux register offset, or config
      register offset if the pin has no mux register, so that kernel can
      identify the pin id from register offsets provided by device tree.
      
      As a bonus point of the change, those arbitrary magic numbers standing
      for particular PIN_FUNC_ID in device tree sources are now replaced by
      macros to improve the readability of dts files.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      Acked-by: NDong Aisheng <dong.aisheng@linaro.org>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      e1641531
    • S
      ARM: imx: use #include for all device trees · 36dffd8f
      Shawn Guo 提交于
      Replace /include/ (dtc) with #include (C pre-processor) for all imx DT
      files, so that gcc -E handles the entire include tree, and hence any of
      those files can #include some other file e.g. for constant definitions.
      
      This allows future use of #defines and header files in order to define
      names for various constants, such as pinctrl settings. Use of those
      features will increase the readability of the device tree files.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      36dffd8f
  11. 10 2月, 2013 3 次提交
    • S
      ARM: dts: add dtsi for imx6q and imx6dl · 7c1da585
      Shawn Guo 提交于
      Add dtsi for imx6q and imx6dl with non-common blocks moved into there.
      Major differences between imx6dl and imx6q:
      
       * Dual vs. Quad cores
       * single vs. dual IPU
       * 128 vs. 256 KB OCRAM
       * imx6q: ECSPI5, OpenVG (GC355), SATA
       * imx6dl: I2C4, PXP, EPDC, LCDIF
       * iomuxc/pads definition
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      7c1da585
    • S
      ARM: dts: rename imx6q.dtsi to imx6qdl.dtsi · 4bacf2a3
      Shawn Guo 提交于
      i.MX6 Quad and i.MX6 DualLite is similar enough to share one dtsi
      file, so rename imx6q.dtsi to imx6qdl.dtsi preparing for the addition
      of imx6dl support.
      
      Another member of i.MX6 series i.MX6 SoloLite is different enough
      from the other two, so it will stand as a separate dtsi.  That's why
      we rename to imx6qdl.dtsi not imx6.dtsi.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      4bacf2a3
    • S
      ARM: dts: imx: use nodes label in board dts · be4ccfce
      Shawn Guo 提交于
      Following omap3-evm.dts way, it changes all imx dts files to use label
      in board dts to refer to nodes defined by soc dtsi.  Thus, the board
      dts files become easier to read and edit with the least indentation
      levels.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      be4ccfce
  12. 19 9月, 2012 1 次提交