On Wed, Jan 29, 2014 at 12:10:48PM +0100, Maxime Ripard wrote:
> +config SPI_SUN6I
> + tristate "Allwinner A31 SPI controller"
> + depends on ARCH_SUNXI || COMPILE_TEST
> + select PM_RUNTIME
> + help
> + This enables using the SPI controller on the Allwinner A31 SoCs.
> +
A select of PM_RUNTIME is both surprising and odd - why is that there?
The usual idiom is that the device starts out powered up (flagged using
pm_runtime_set_active()) and then runtime PM then suspends it when it's
compiled in. That way if for some reason people want to avoid runtime
PM they can still use the device.
> +static void sun6i_spi_set_cs(struct spi_device *spi, bool enable)
> +{
> + struct sun6i_spi *sspi = spi_master_get_devdata(spi->master);
> + u32 reg;
> +
> + if (!enable)
> + return;
> +
> + reg = sun6i_spi_read(sspi, SUN6I_TFR_CTL_REG);
> + reg &= ~SUN6I_TFR_CTL_CS_MASK;
> + reg |= SUN6I_TFR_CTL_CS(spi->chip_select);
> + sun6i_spi_write(sspi, SUN6I_TFR_CTL_REG, reg);
> +}
The !enable means that it'll only ever be able to go one way. Also note
that the documentation was clarified here to make the enable flag be the
absolute logic level, not if chip select was asserted.
> + timeout = wait_for_completion_timeout(&sspi->done,
> + msecs_to_jiffies(1000));
> + if (!timeout) {
> + ret = -ETIMEDOUT;
> + goto out;
> + }
> +
> + sun6i_spi_drain_fifo(sspi, SUN6I_FIFO_DEPTH);
This means we can only transfer a single FIFO of data? I didn't see a
check on the transfer length.
Attachment:
signature.asc
Description: Digital signature
