On 24/09/2023 14:22, Ayush Singh wrote: >> So this is "Texas Instruments Simplelink CC1352P7 wireless MCU"? Since >> you do not have any fixed feature and run general-purpose OS, then this >> should be rather compatible matching actual hardware (so ti,cc1352p7). > Yes, 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`? Zephyr bindings might be entirely different, because they are for the case of running Zephyr OS on this processor. I still do not fully understand whether you describe here generic MCU used for Greybus or some specific firmware with fixed features. Looks like the first, thus my suggestion about compatible. The location could be arm. >> >>> + >>> +maintainers: >>> + - Ayush Singh <ayushdevel1325@xxxxxxxxx> >>> + >>> +properties: >>> + compatible: >>> + const: beagle,play-cc1352 >>> + >>> +required: >>> + - compatible >> Still no resources? I asked about it last time and you did not answer >> anything. > Sorry, I missed that. By resources, I think you mean pins, peripherals, > etc right? By resources I mean whatever is needed to power it up and operate, e.g. clocks, supplies, reset lines. Best regards, Krzysztof _______________________________________________ greybus-dev mailing list -- greybus-dev@xxxxxxxxxxxxxxxx To unsubscribe send an email to greybus-dev-leave@xxxxxxxxxxxxxxxx
|