CCing devicetree and SPI maintainers.
On 08/07/2013 09:54 AM, leroy christophe wrote:
> This patch allows to set up the bits per word together with all other SPI
> parameters in the SPI Node of the OF device tree
The new property needs to be documented somewhere in
Documentation/devicetree/bindings.
> In the node, you then have to include the 'spi-bits' property.
>
> Exemple:
> fpga-loader@7 {
> compatible = "cs,fpga-loader";
> spi-max-frequency = <10000000>;
> reg = <7>;
> spi-cs-high;
> spi-bits = <16>;
> };
Shouldn't the driver for cs,fpga-loader be defining how many bit the SPI
transactions should use? If the binding covers HW that can operate at
various bits-per-word, it's reasonable for those individual bindings to
define a property that sets that width, but I'm not convinced it's
reasonable for the SPI core to allow any DT node to specify that, and
presumably override the SPI device's driver's selection.
> --- linux-3.8.13/drivers/spi/spi.c 2013-05-11 22:57:46.000000000 +0200
> +++ linux/drivers/spi/spi.c 2013-08-06 18:19:30.000000000 +0200
> @@ -870,6 +870,11 @@
> if (of_find_property(nc, "spi-3wire", NULL))
> spi->mode |= SPI_3WIRE;
> + /* Bits per word */
> + prop = of_get_property(nc, "spi-bits", &len);
> + if (prop && len >= sizeof(*prop))
> + spi->bits_per_word = prop[0];
> +
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
