summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/tty
diff options
context:
space:
mode:
authorStephen Boyd <sboyd@codeaurora.org>2013-08-28 13:32:40 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-08-28 16:03:29 -0700
commit6e01365c469f3cfe96a1b428bade1a3628896929 (patch)
treec84de7b9b5cd00c518f0330ea54eca817cd130f7 /Documentation/devicetree/bindings/tty
parent6b9c1fa25a5c2a2a2d8fa1e2f8c2cc5d6d0c4a45 (diff)
downloadblackbird-obmc-linux-6e01365c469f3cfe96a1b428bade1a3628896929.tar.gz
blackbird-obmc-linux-6e01365c469f3cfe96a1b428bade1a3628896929.zip
devicetree: serial: Document msm_serial bindings
Let's fix up the msm serial device bindings so that it's clearer what hardware is supported. Instead of using hsuart (for high speed uart) let's use uartdm because that matches the actual name of the hardware. Also, let's add the version information in case we need to differentiate between different versions of the hardware in the future. Finally, lets specify that clocks are required (the clock bindings didn't exist when the original binding was written) and also specify dma bindings just in case we want to use it in software. We split the binding into two files to make it clearer what's required and not required. Cc: David Brown <davidb@codeaurora.org> Cc: <devicetree@vger.kernel.org> Acked-by: Kumar Gala <galak@codeaurora.org> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/devicetree/bindings/tty')
-rw-r--r--Documentation/devicetree/bindings/tty/serial/msm_serial.txt27
1 files changed, 0 insertions, 27 deletions
diff --git a/Documentation/devicetree/bindings/tty/serial/msm_serial.txt b/Documentation/devicetree/bindings/tty/serial/msm_serial.txt
deleted file mode 100644
index aef383eb8876..000000000000
--- a/Documentation/devicetree/bindings/tty/serial/msm_serial.txt
+++ /dev/null
@@ -1,27 +0,0 @@
-* Qualcomm MSM UART
-
-Required properties:
-- compatible :
- - "qcom,msm-uart", and one of "qcom,msm-hsuart" or
- "qcom,msm-lsuart".
-- reg : offset and length of the register set for the device
- for the hsuart operating in compatible mode, there should be a
- second pair describing the gsbi registers.
-- interrupts : should contain the uart interrupt.
-
-There are two different UART blocks used in MSM devices,
-"qcom,msm-hsuart" and "qcom,msm-lsuart". The msm-serial driver is
-able to handle both of these, and matches against the "qcom,msm-uart"
-as the compatibility.
-
-The registers for the "qcom,msm-hsuart" device need to specify both
-register blocks, even for the common driver.
-
-Example:
-
- uart@19c400000 {
- compatible = "qcom,msm-hsuart", "qcom,msm-uart";
- reg = <0x19c40000 0x1000>,
- <0x19c00000 0x1000>;
- interrupts = <195>;
- };
OpenPOWER on IntegriCloud