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:00:26 +0200 [thread overview]
Message-ID: <0fd912a9-4aaa-d4bd-4ceb-7319d9f46db8@linaro.org> (raw)
In-Reply-To: <20230924113725.164948-2-ayushdevel1325@gmail.com>
On 24/09/2023 13:36, Ayush Singh wrote:
> Adds DT bindings for BeaglePlay CC1352 co-processor.
I gave you the link to the exact wording you should use. "Add", not
"Adds". The latter is not a correct English sentences, I believe.
>
> BeaglePlay has a CC1352 co-processor connected to the main AM62 (running
> Linux) over UART. In the BeagleConnect Technology, CC1352 is responsible
> for handling 6LoWPAN communication with beagleconnect freedom nodes as
> well as their discovery.
>
> It is used by gb-beagleplay greybus driver.
>
> Signed-off-by: Ayush Singh <ayushdevel1325@gmail.com>
> ---
> .../bindings/net/beagle,play-cc1352.yaml | 25 +++++++++++++++++++
> MAINTAINERS | 6 +++++
> 2 files changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/beagle,play-cc1352.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/beagle,play-cc1352.yaml b/Documentation/devicetree/bindings/net/beagle,play-cc1352.yaml
> new file mode 100644
> index 000000000000..f8536d1a6765
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/beagle,play-cc1352.yaml
> @@ -0,0 +1,25 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/beagle,play-cc1352.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: BeaglePlay CC1352 co-processor
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).
> +
> +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.
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + mcu {
> + compatible = "beagle,play-cc1352";
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 37b9626ee654..9d1b49a6dfad 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8969,6 +8969,12 @@ F: drivers/staging/greybus/sdio.c
> F: drivers/staging/greybus/spi.c
> F: drivers/staging/greybus/spilib.c
>
> +GREYBUS BEAGLEPLAY DRIVERS
> +M: Ayush Singh <ayushdevel1325@gmail.com>
> +L: greybus-dev@lists.linaro.org (moderated for non-subscribers)
> +S: Maintained
> +F: Documentation/devicetree/bindings/serial/beaglecc1352.yaml
That's not a correct path.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-24 12:00 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 [this message]
2023-09-24 12:22 ` Ayush Singh
2023-09-24 12:53 ` Krzysztof Kozlowski
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=0fd912a9-4aaa-d4bd-4ceb-7319d9f46db8@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;
as well as URLs for NNTP newsgroup(s).