driver.
Signed-off-by: Ayush Singh ayushdevel1325@gmail.com
.../devicetree/bindings/net/ti,cc1352p7.yaml | 48 +++++++++++++++++++ MAINTAINERS | 6 +++ 2 files changed, 54 insertions(+) create mode 100644 Documentation/devicetree/bindings/net/ti,cc1352p7.yaml
diff --git a/Documentation/devicetree/bindings/net/ti,cc1352p7.yaml b/Documentation/devicetree/bindings/net/ti,cc1352p7.yaml new file mode 100644 index 000000000000..57bc2c43e5b1 --- /dev/null +++ b/Documentation/devicetree/bindings/net/ti,cc1352p7.yaml @@ -0,0 +1,48 @@ +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/net/ti,cc1352p7.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml#
+title: Texas Instruments Simplelink CC1352P7 wireless MCU
+description:
- The cc1352p7 mcu can be connected via SPI or UART.
If over SPI, then the binding is incomplete. This is fine for now, I guess.
Best regards, Krzysztof
Well, I added the line about SPI because the data sheet states that CC1352P7 can be connected over SPI or UART when used as wireless MCU. But yes, I do not have much knowledge about SPI itself, so the bindings might be incomplete for SPI usage. Should I remove it or leave it be?
Sincerely,
Ayush Singh