1. 06 Mar, 2020 1 commit
  2. 05 Mar, 2020 21 commits
  3. 04 Mar, 2020 7 commits
    • Mark Brown's avatar
      Merge series "Compatible string consolidation for NXP DSPI driver" from... · cb71d8ef
      Mark Brown authored
      Merge series "Compatible string consolidation for NXP DSPI driver" from Vladimir Oltean <olteanv@gmail.com>:
      
      This series makes room in the driver for differentiation between the
      controllers which currently operate in TCFQ mode. Most of these are
      actually capable of a lot more in terms of throughput. This is in
      preparation of a second series which will convert the remaining users of
      TCFQ mode altogether to XSPI mode with command cycling.
      
      Vladimir Oltean (6):
        doc: spi-fsl-dspi: Add specific compatibles for all Layerscape SoCs
        spi: spi-fsl-dspi: Use specific compatible strings for all SoC
          instantiations
        spi: spi-fsl-dspi: Parameterize the FIFO size and DMA buffer size
        spi: spi-fsl-dspi: LS2080A and LX2160A support XSPI mode
        spi: spi-fsl-dspi: Support SPI software timestamping in all non-DMA
          modes
        spi: spi-fsl-dspi: Convert the instantiations that support it to DMA
      
       .../devicetree/bindings/spi/spi-fsl-dspi.txt  |  17 +-
       drivers/spi/spi-fsl-dspi.c                    | 162 +++++++++++++-----
       2 files changed, 128 insertions(+), 51 deletions(-)
      
      --
      2.17.1
      cb71d8ef
    • Vladimir Oltean's avatar
      spi: spi-fsl-dspi: Add specific compatibles for all Layerscape SoCs · 50b62071
      Vladimir Oltean authored
      Make the second compatible string optional for LS1012A, LS1088A and
      LS2080A. Old versions of the spi-fsl-dspi.c driver still need to probe
      on the old, generic compatible string for these controllers (such as
      "fsl,ls1021a-v1.0-dspi") which provides less functionality.
      
      Document the device tree bindings for LS1043A and LS1046A, whose
      bindings are already in use in fsl-ls1043a.dtsi and fsl-ls1046a.dtsi.
      
      Introduce new compatible strings for LS1028A and LX2160A. There will be
      no second compatible string for these.
      Signed-off-by: default avatarVladimir Oltean <vladimir.oltean@nxp.com>
      Message-Id: <20200302001958.11105-2-olteanv@gmail.com>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      50b62071
    • Vladimir Oltean's avatar
      spi: spi-fsl-dspi: Convert the instantiations that support it to DMA · 0feaf8f5
      Vladimir Oltean authored
      The A-011218 eDMA/DSPI erratum affects most of the older Layerscape SoCs
      with DSPI, and its workaround is a bit intrusive.
      
      After this patch, there are no users of TCFQ mode that don't also
      support XSPI (previously there was LS2085A).
      Signed-off-by: default avatarVladimir Oltean <vladimir.oltean@nxp.com>
      Message-Id: <20200302001958.11105-7-olteanv@gmail.com>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      0feaf8f5
    • Vladimir Oltean's avatar
      spi: spi-fsl-dspi: Support SPI software timestamping in all non-DMA modes · 63669902
      Vladimir Oltean authored
      There's no reason to keep this .ptp_sts_supported property explicitly in
      devtype_data, since it can be deduced from the operating mode alone.
      Signed-off-by: default avatarVladimir Oltean <vladimir.oltean@nxp.com>
      Message-Id: <20200302001958.11105-6-olteanv@gmail.com>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      63669902
    • Vladimir Oltean's avatar
      spi: spi-fsl-dspi: LS2080A and LX2160A support XSPI mode · ca5052c8
      Vladimir Oltean authored
      XSPI allows for 2 extra features:
      - Command cycling (use a single TX command with more than 1 word in the
        TX FIFO).
      - Increased word size (from 16 bits to 32 bits)
      Signed-off-by: default avatarVladimir Oltean <vladimir.oltean@nxp.com>
      Message-Id: <20200302001958.11105-5-olteanv@gmail.com>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      ca5052c8
    • Vladimir Oltean's avatar
      spi: spi-fsl-dspi: Parameterize the FIFO size and DMA buffer size · 1d8b4c95
      Vladimir Oltean authored
      Get rid of the ifdef for Coldfire and make these hardware
      characteristics part of dspi->devtype_data.
      Signed-off-by: default avatarVladimir Oltean <vladimir.oltean@nxp.com>
      Message-Id: <20200302001958.11105-4-olteanv@gmail.com>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      1d8b4c95
    • Vladimir Oltean's avatar
      spi: spi-fsl-dspi: Use specific compatible strings for all SoC instantiations · d3505401
      Vladimir Oltean authored
      Currently, the device tree bindings submitted in mainline for Layerscape
      SoCs look like this:
      
      LS1021A:
      compatible = "fsl,ls1021a-v1.0-dspi";
      
      LS1012A:
      compatible = "fsl,ls1012a-dspi", "fsl,ls1021a-v1.0-dspi";
      
      LS2085A:
      compatible = "fsl,ls2085a-dspi";
      
      LS2088A:
      compatible = "fsl,ls2080a-dspi", "fsl,ls2085a-dspi";
      
      LX2160A:
      compatible = "fsl,lx2160a-dspi", "fsl,ls2085a-dspi";
      
      LS1043A:
      compatible = "fsl,ls1043a-dspi", "fsl,ls1021a-v1.0-dspi";
      
      LS1046A:
      compatible = "fsl,ls1021a-v1.0-dspi";
      
      Due to a lack of a more specific compatible string, LS1012A, LS1043A and
      LS1046A will fall under the LS1021A umbrella, and LS2088A and LX2160A
      under the LS2085A umbrella.
      
      They do work in those modes, but there are slight differences in the
      hardware instantiations, mostly related to FIFO sizes (with the more
      specific compatible strings, the FIFO size can be increased properly).
      Signed-off-by: default avatarVladimir Oltean <vladimir.oltean@nxp.com>
      Message-Id: <20200302001958.11105-3-olteanv@gmail.com>
      Signed-off-by: default avatarMark Brown <broonie@kernel.org>
      d3505401
  4. 03 Mar, 2020 4 commits
  5. 02 Mar, 2020 7 commits