* [PATCH 1/2] DT: Add documentation for spi-rt2880
@ 2013-08-09 18:51 John Crispin
2013-08-09 20:44 ` Sergei Shtylyov
2013-08-09 23:35 ` Kumar Gala
0 siblings, 2 replies; 3+ messages in thread
From: John Crispin @ 2013-08-09 18:51 UTC (permalink / raw)
To: Mark Brown; +Cc: John Crispin, devicetree, linux-spi, linux-mips
Describe the SPI master found on the MIPS based Ralink SoC.
Signed-off-by: John Crispin <blogic@openwrt.org>
Cc: devicetree@vger.kernel.org
Cc: linux-spi@vger.kernel.org
Cc: linux-mips@linux-mips.org
---
.../devicetree/bindings/spi/spi-rt2880.txt | 26 ++++++++++++++++++++
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-rt2880.txt
diff --git a/Documentation/devicetree/bindings/spi/spi-rt2880.txt b/Documentation/devicetree/bindings/spi/spi-rt2880.txt
new file mode 100644
index 0000000..d946626
--- /dev/null
+++ b/Documentation/devicetree/bindings/spi/spi-rt2880.txt
@@ -0,0 +1,26 @@
+Ralink SoC RT2880 and famile SPI master controller.
+
+Required properties:
+- compatible : "ralink,rt2880-spi"
+- reg : The register base for the controller.
+- #address-cells : <1>, as required by generic SPI binding.
+- #size-cells : <0>, also as required by generic SPI binding.
+
+Child nodes as per the generic SPI binding.
+
+Example:
+
+ spi@b00 {
+ compatible = "ralink,rt2880-spi";
+ reg = <0xb00 0x100>;
+
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ m25p80@0 {
+ compatible = "m25p80";
+ reg = <0>;
+ spi-max-frequency = <10000000>;
+ };
+ };
+
--
1.7.10.4
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH 1/2] DT: Add documentation for spi-rt2880
2013-08-09 18:51 [PATCH 1/2] DT: Add documentation for spi-rt2880 John Crispin
@ 2013-08-09 20:44 ` Sergei Shtylyov
2013-08-09 23:35 ` Kumar Gala
1 sibling, 0 replies; 3+ messages in thread
From: Sergei Shtylyov @ 2013-08-09 20:44 UTC (permalink / raw)
To: John Crispin; +Cc: Mark Brown, devicetree, linux-spi, linux-mips
Hello.
On 08/09/2013 10:51 PM, John Crispin wrote:
> Describe the SPI master found on the MIPS based Ralink SoC.
> Signed-off-by: John Crispin <blogic@openwrt.org>
> Cc: devicetree@vger.kernel.org
> Cc: linux-spi@vger.kernel.org
> Cc: linux-mips@linux-mips.org
> ---
> .../devicetree/bindings/spi/spi-rt2880.txt | 26 ++++++++++++++++++++
> 1 file changed, 26 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/spi/spi-rt2880.txt
> diff --git a/Documentation/devicetree/bindings/spi/spi-rt2880.txt b/Documentation/devicetree/bindings/spi/spi-rt2880.txt
> new file mode 100644
> index 0000000..d946626
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/spi-rt2880.txt
> @@ -0,0 +1,26 @@
> +Ralink SoC RT2880 and famile SPI master controller.
> +
> +Required properties:
> +- compatible : "ralink,rt2880-spi"
> +- reg : The register base for the controller.
> +- #address-cells : <1>, as required by generic SPI binding.
> +- #size-cells : <0>, also as required by generic SPI binding.
> +
> +Child nodes as per the generic SPI binding.
> +
> +Example:
> +
> + spi@b00 {
> + compatible = "ralink,rt2880-spi";
> + reg = <0xb00 0x100>;
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + m25p80@0 {
Don't call nodes with chip names. ePAPR [1] says: "the name of a node
should be somewhat generic, reflecting the function of the device and not its
precise programming model". I suspect this is a flash device, ePAPR suggests
using "flash" as a name in this case.
> + compatible = "m25p80";
> + reg = <0>;
> + spi-max-frequency = <10000000>;
> + };
> + };
> +
WBR, Sergei
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 1/2] DT: Add documentation for spi-rt2880
2013-08-09 18:51 [PATCH 1/2] DT: Add documentation for spi-rt2880 John Crispin
2013-08-09 20:44 ` Sergei Shtylyov
@ 2013-08-09 23:35 ` Kumar Gala
1 sibling, 0 replies; 3+ messages in thread
From: Kumar Gala @ 2013-08-09 23:35 UTC (permalink / raw)
To: John Crispin; +Cc: Mark Brown, devicetree, linux-spi, linux-mips
On Aug 9, 2013, at 1:51 PM, John Crispin wrote:
> Describe the SPI master found on the MIPS based Ralink SoC.
Ralink RT2880 SoC
>
> Signed-off-by: John Crispin <blogic@openwrt.org>
> Cc: devicetree@vger.kernel.org
> Cc: linux-spi@vger.kernel.org
> Cc: linux-mips@linux-mips.org
> ---
> .../devicetree/bindings/spi/spi-rt2880.txt | 26 ++++++++++++++++++++
> 1 file changed, 26 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/spi/spi-rt2880.txt
>
> diff --git a/Documentation/devicetree/bindings/spi/spi-rt2880.txt b/Documentation/devicetree/bindings/spi/spi-rt2880.txt
> new file mode 100644
> index 0000000..d946626
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/spi-rt2880.txt
> @@ -0,0 +1,26 @@
> +Ralink SoC RT2880 and famile SPI master controller.
famile? was that suppose to be family?
> +
> +Required properties:
> +- compatible : "ralink,rt2880-spi"
> +- reg : The register base for the controller.
> +- #address-cells : <1>, as required by generic SPI binding.
> +- #size-cells : <0>, also as required by generic SPI binding.
> +
> +Child nodes as per the generic SPI binding.
> +
> +Example:
> +
> + spi@b00 {
> + compatible = "ralink,rt2880-spi";
> + reg = <0xb00 0x100>;
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + m25p80@0 {
> + compatible = "m25p80";
> + reg = <0>;
> + spi-max-frequency = <10000000>;
> + };
> + };
> +
> --
> 1.7.10.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-08-09 23:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-09 18:51 [PATCH 1/2] DT: Add documentation for spi-rt2880 John Crispin
2013-08-09 20:44 ` Sergei Shtylyov
2013-08-09 23:35 ` Kumar Gala
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).