On 10/08/2014 03:05 PM, Mark Brown wrote:
On Wed, Oct 08, 2014 at 02:27:08PM -0500, tthayer@xxxxxxxxxxxxxxxxxxxxx wrote:
+ spidev@0 {
+ compatible = "spidev";
+ reg = <0>; /* chip select */
+ spi-max-frequency = <100000000>;
+ };
No, if you're putting spidev into the DT that's broken - describe the
hardware, not the software you're using to control it.
Hi Mark,
There are quite a few instances of the spidev as a child of a spi node
in the arch/arm/dts directory
- imx6qdl-tx6.dtsi
- imx53-tx53.dtsi
- tegra30-apalis-eval.dts
- spear1340-evb.dts
I believe the reason these are added to the device tree is that they are
automatically probed.
If there is a different or better way to handle spidev, I'll be happy to
do it. This seemed to be the cleanest way and had precedent.
Thanks for reviewing this and I appreciate your input.
Thor
--
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
