On Wed, Jun 15, 2011 at 1:25 PM, Stephen Warren <swar...@nvidia.com> wrote: > Grant Likely wrote at Wednesday, June 15, 2011 1:08 PM: >> Allow the tegra spi driver to obtain populate the spi bus with devices > > Remote "obtain"?
heh, oops. > >> from the device tree. >> >> Signed-off-by: Grant Likely <grant.lik...@secretlab.ca> >> --- >> .../devicetree/bindings/spi/spi_nvidia.txt | 5 +++++ >> drivers/spi/spi-tegra.c | 12 ++++++++++++ >> 2 files changed, 17 insertions(+), 0 deletions(-) >> create mode 100644 Documentation/devicetree/bindings/spi/spi_nvidia.txt >> >> diff --git a/Documentation/devicetree/bindings/spi/spi_nvidia.txt >> b/Documentation/devicetree/bindings/spi/spi_nvidia.txt >> new file mode 100644 >> index 0000000..bde450b >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/spi/spi_nvidia.txt >> @@ -0,0 +1,5 @@ >> +NVIDIA Tegra 2 SPI device >> + >> +Required properties: >> +- compatible : should be "nvidia,tegra250-spi". >> +- gpios : should specify GPIOs used for chipselect. > > Are things like reg, interrupts, and other general stuff implicit? > I notice that fsl-spi.txt does specify those, but spi_altera.txt > and spi_oc_tiny.txt don't. yeah, standard properties are pretty much implicit. I don't bother writing the words if there isn't much value to them. I've been contemplating a tool that will take DT documentation written in a certain form, and automatically fill in standard properties as needed, but that's a project for another day. g. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
