Re: [PATCH v4 1/3] dt-bindings: Add beaglecc1352

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


On 9/4/23 12:44, Krzysztof Kozlowski wrote:
On 02/09/2023 20:28, Ayush Singh wrote:
Add DT bindings for BeagleCC1352 co-processor UART.
This does not look like UART controller.

Signed-off-by: Ayush Singh <ayushdevel1325@xxxxxxxxx>
  .../bindings/serial/beaglecc1352.yaml         | 25 +++++++++++++++++++
It's not a serial driver. Don't put it in unrelated directory.

@@ -0,0 +1,25 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+title: BeaglePlay CC1352 serial UART
How is this serial UART? Of what? The SoC? Do not describe interface but
the device.

+  - Ayush Singh <ayushdevel1325@xxxxxxxxx>
+  compatible:
+    const: beagle,cc1352
No resources? This does not seem useful... Put it then only in trivial
devices if your hardware - hardware, not driver - does not have any
pins, interrupts or other resources.

+  - compatible
+additionalProperties: false
+  - |
+    beaglecc1352 {
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:

Best regards,

I would like to get some help on how to tackle this particular device since I cannot seem to find anything similar to this setup. First let me go over the setup.

The BeaglePlay board has 2 processors. AM625 processor which is the main processor. This runs the main Linux system. This processor does not have direct access to SubG.

It also contains a CC1352P7 MCU with it's own flash program memory, ROM and SRAM. This processor has SubG antenna. It runs it's own OS (Zephyr by default).

The only way for CC1352P7 and AM625 to communicate is by using that particular UART which is just a standard 8250 UART. The setup pretty much looks like 2 boards connected over UART except the UART will always be static.

I guess it would make most sense to write a CC1352P7 binding in this case? However, I am not sure how accurate that is since anything from the Linux side will be interacting with the Zephyr application, and not the processor. So in all actuality, the processor itself does not matter at all.

Ayush Singh

greybus-dev mailing list -- greybus-dev@xxxxxxxxxxxxxxxx
To unsubscribe send an email to greybus-dev-leave@xxxxxxxxxxxxxxxx

[Index of Archives]     [Asterisk App Development]     [PJ SIP]     [Gnu Gatekeeper]     [IETF Sipping]     [Info Cyrus]     [ALSA User]     [Fedora Linux Users]     [Linux SCTP]     [DCCP]     [Gimp]     [Yosemite News]     [Deep Creek Hot Springs]     [Yosemite Campsites]     [ISDN Cause Codes]     [Asterisk Books]

  Powered by Linux