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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <141ec8de-4008-9f96-e915-92056b409edc@linaro.org>
Date:   Sun, 24 Sep 2023 14:53:54 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Ayush Singh <ayushdevel1325@...il.com>,
        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

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@...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?

By resources I mean whatever is needed to power it up and operate, e.g.
clocks, supplies, reset lines.

Best regards,
Krzysztof