[PATCH v5 1/3] dt-bindings: Add beagleplaycc1352

Ayush Singh ayushdevel1325 at gmail.com
Sun Sep 24 05:22:33 PDT 2023


> 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`?
>
>> +
>> +maintainers:
>> +  - Ayush Singh <ayushdevel1325 at gmail.com>
>> +
>> +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?


Ayush Singh




More information about the linux-arm-kernel mailing list