From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ayush Singh <ayushdevel1325@gmail.com>, greybus-dev@lists.linaro.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, vaishnav@beagleboard.org,
jkridner@beagleboard.org, nm@ti.com,
krzysztof.kozlowski+dt@linaro.org, vigneshr@ti.com,
kristo@kernel.org, robh+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 1/3] dt-bindings: Add beagleplaycc1352
Date: Sun, 24 Sep 2023 14:53:54 +0200 [thread overview]
Message-ID: <141ec8de-4008-9f96-e915-92056b409edc@linaro.org> (raw)
In-Reply-To: <69f8f5aa-075c-0dc1-7a5f-bd6978c71f53@gmail.com>
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@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?
By resources I mean whatever is needed to power it up and operate, e.g.
clocks, supplies, reset lines.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-24 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 11:36 [PATCH v5 0/3] greybus: Add BeaglePlay Greybus Driver Ayush Singh
2023-09-24 11:36 ` [PATCH v5 1/3] dt-bindings: Add beagleplaycc1352 Ayush Singh
2023-09-24 12:00 ` Krzysztof Kozlowski
2023-09-24 12:22 ` Ayush Singh
2023-09-24 12:53 ` Krzysztof Kozlowski [this message]
2023-09-24 11:36 ` [PATCH v5 2/3] greybus: Add BeaglePlay Linux Driver Ayush Singh
2023-09-24 12:04 ` Krzysztof Kozlowski
2023-09-24 12:32 ` Ayush Singh
2023-09-24 12:55 ` Krzysztof Kozlowski
2023-09-24 13:08 ` Ayush Singh
2023-10-01 18:13 ` Ayush Singh
2023-10-02 13:51 ` Krzysztof Kozlowski
2023-09-24 11:36 ` [PATCH v5 3/3] dts: ti: k3-am625-beagleplay: Add beaglecc1352 Ayush Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=141ec8de-4008-9f96-e915-92056b409edc@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=ayushdevel1325@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jkridner@beagleboard.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vaishnav@beagleboard.org \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®