So this is "Texas Instruments Simplelink CC1352P7 wireless MCU"? SinceYes, it is "Texas Instruments Simplelink CC1352P7 wireless MCU". Since the docs suggest that all functionality of the device should be mentioned in the bindings rather than just what is being used, I suppose all the other properties can be defined as optional? The bindings for this device do exist in Zephyr, so I guess that can be re-purposed for Linux kernel. However, I think in that case it should be moved into `soc` instead of `net`?
you do not have any fixed feature and run general-purpose OS, then this
should be rather compatible matching actual hardware (so ti,cc1352p7).
Sorry, I missed that. By resources, I think you mean pins, peripherals, etc right?
+Still no resources? I asked about it last time and you did not answer
+maintainers:
+ - Ayush Singh <ayushdevel1325@xxxxxxxxx>
+
+properties:
+ compatible:
+ const: beagle,play-cc1352
+
+required:
+ - compatible
anything.