[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69f8f5aa-075c-0dc1-7a5f-bd6978c71f53@gmail.com>
Date: Sun, 24 Sep 2023 17:52:33 +0530
From: Ayush Singh <ayushdevel1325@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
greybus-dev@...ts.linaro.org
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
gregkh@...uxfoundation.org, vaishnav@...gleboard.org,
jkridner@...gleboard.org, nm@...com,
krzysztof.kozlowski+dt@...aro.org, vigneshr@...com,
kristo@...nel.org, robh+dt@...nel.org, conor+dt@...nel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 1/3] dt-bindings: Add beagleplaycc1352
> 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@...il.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
Powered by blists - more mailing lists