Re: [PATCH v2] spi: img-spfi: Same Edge bit set to double supported transfer speed

[Jonas Gorski <jogo@xxxxxxxxxxx>]

Hi,

On Wed, Jun 17, 2015 at 12:01 PM, Sifan Naeem <sifan.naeem@xxxxxxxxxx> wrote:
> Same edge bit set in SPFI Control register to double the supported
> spfi clock speed. Setting this bit increases the supported spfi
> frequency from 1/8 to 1/4 of the core clock frequency.
>
> Without this bit set the maximum speed supported was 25MHz on
> Pistachio.
>
> Change-Id: I26782ea88ac3567e72dac11e46c5b5f5f52c5e3d
> Signed-off-by: Sifan Naeem <sifan.naeem@xxxxxxxxxx>
> ---
>  drivers/spi/spi-img-spfi.c |    2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/spi/spi-img-spfi.c b/drivers/spi/spi-img-spfi.c
> index 788e2b1..acce90a 100644
> --- a/drivers/spi/spi-img-spfi.c
> +++ b/drivers/spi/spi-img-spfi.c
> @@ -40,6 +40,7 @@
>  #define SPFI_CONTROL_SOFT_RESET                        BIT(11)
>  #define SPFI_CONTROL_SEND_DMA                  BIT(10)
>  #define SPFI_CONTROL_GET_DMA                   BIT(9)
> +#define SPFI_CONTROL_SE                        BIT(8)
>  #define SPFI_CONTROL_TMODE_SHIFT               5
>  #define SPFI_CONTROL_TMODE_MASK                        0x7
>  #define SPFI_CONTROL_TMODE_SINGLE              0
> @@ -491,6 +492,7 @@ static void img_spfi_config(struct spi_master *master, struct spi_device *spi,
>         else if (xfer->tx_nbits == SPI_NBITS_QUAD &&
>                  xfer->rx_nbits == SPI_NBITS_QUAD)
>                 val |= SPFI_CONTROL_TMODE_QUAD << SPFI_CONTROL_TMODE_SHIFT;
> +       val |= SPFI_CONTROL_SE;
>         spfi_writel(spfi, val, SPFI_CONTROL);
>  }

Don't you also need to update master->max_speed_hz? And if it doubles
the clock speed, don't you need to reflect that in the calculation for
the devider? Currently it looks like it would just cause all transfers
to go with the doubled requested rate. But maybe I'm missing
something.


Regards
Jonas
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html