public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Michael Nemanov <michael.nemanov@ti.com>,
	Kalle Valo <kvalo@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Sabeeh Khan <sabeeh-khan@ti.com>
Subject: Re: [PATCH v4 01/17] dt-bindings: net: wireless: cc33xx: Add ti,cc33xx.yaml
Date: Tue, 29 Oct 2024 18:28:52 +0100	[thread overview]
Message-ID: <936b19eb-cde7-4be8-98cf-e60e32b335cd@kernel.org> (raw)
In-Reply-To: <20241029172354.4027886-2-michael.nemanov@ti.com>

On 29/10/2024 18:23, Michael Nemanov wrote:
> Add device-tree bindings for the CC33xx family.
> 
> Signed-off-by: Michael Nemanov <michael.nemanov@ti.com>
> ---
>  .../bindings/net/wireless/ti,cc33xx.yaml      | 59 +++++++++++++++++++
>  1 file changed, 59 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/net/wireless/ti,cc33xx.yaml
> 
> diff --git a/Documentation/devicetree/bindings/net/wireless/ti,cc33xx.yaml b/Documentation/devicetree/bindings/net/wireless/ti,cc33xx.yaml
> new file mode 100644
> index 000000000000..12a0a2f52f44
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/wireless/ti,cc33xx.yaml
> @@ -0,0 +1,59 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/wireless/ti,cc33xx.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments CC33xx Wireless LAN Controller
> +
> +maintainers:
> +  - Michael Nemanov <michael.nemanov@ti.com>
> +
> +description:
> +  The CC33xx is a family of IEEE 802.11ax chips from Texas Instruments.
> +  These chips must be connected via SDIO and support in-band / out-of-band IRQ.
> +
> +properties:
> +  $nodename:
> +    pattern: "^wifi@2"

This wasn't here, please drop.

> +
> +  compatible:
> +    oneOf:

Why oneOf appeared? Do you plan to grow it?

> +      - items:
> +          - enum:
> +              - ti,cc3300
> +              - ti,cc3301
> +              - ti,cc3350
> +              - ti,cc3351
> +          - const: ti,cc33xx

And how cc33xx could appear? That's a no. Generic compatibles are not
allowed. Please do not introduce some completely different changes than
asked for.

Your changelog does not explain these three. "Fixed compatibility" is
way too vague, especially that you do not fix anything here.

> +
> +  reg:
> +    const: 2
> +

Best regards,
Krzysztof


  reply	other threads:[~2024-10-29 17:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 17:23 [PATCH v4 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 01/17] dt-bindings: net: wireless: cc33xx: Add ti,cc33xx.yaml Michael Nemanov
2024-10-29 17:28   ` Krzysztof Kozlowski [this message]
2024-10-30 10:59     ` Nemanov, Michael
2024-10-30 11:09       ` Krzysztof Kozlowski
2024-10-30 12:14         ` Nemanov, Michael
2024-10-30 14:01           ` Krzysztof Kozlowski
2024-10-29 17:23 ` [PATCH v4 02/17] wifi: cc33xx: Add cc33xx.h, cc33xx_i.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 03/17] wifi: cc33xx: Add debug.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 04/17] wifi: cc33xx: Add sdio.c, io.c, io.h Michael Nemanov
2024-10-29 17:34   ` Krzysztof Kozlowski
2024-11-03 13:33     ` Nemanov, Michael
2024-10-29 17:23 ` [PATCH v4 05/17] wifi: cc33xx: Add cmd.c, cmd.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 06/17] wifi: cc33xx: Add acx.c, acx.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 07/17] wifi: cc33xx: Add event.c, event.h Michael Nemanov
2024-11-02 13:12   ` Simon Horman
2024-10-29 17:23 ` [PATCH v4 08/17] wifi: cc33xx: Add boot.c, boot.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 09/17] wifi: cc33xx: Add main.c Michael Nemanov
2024-11-02 13:25   ` Simon Horman
2024-11-03 12:55     ` Nemanov, Michael
2024-10-29 17:23 ` [PATCH v4 10/17] wifi: cc33xx: Add rx.c, rx.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 11/17] wifi: cc33xx: Add tx.c, tx.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 12/17] wifi: cc33xx: Add init.c, init.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 13/17] wifi: cc33xx: Add scan.c, scan.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 14/17] wifi: cc33xx: Add conf.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 15/17] wifi: cc33xx: Add ps.c, ps.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 16/17] wifi: cc33xx: Add testmode.c, testmode.h Michael Nemanov
2024-10-29 17:23 ` [PATCH v4 17/17] wifi: cc33xx: Add Kconfig, Makefile Michael Nemanov
2024-10-29 17:55   ` Krzysztof Kozlowski

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=936b19eb-cde7-4be8-98cf-e60e32b335cd@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michael.nemanov@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=sabeeh-khan@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