From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jacobe Zang <jacobe.zang@wesion.com>, arend.vanspriel@broadcom.com
Cc: kvalo@kernel.org, duoming@zju.edu.cn, bhelgaas@google.com,
minipli@grsecurity.net, linux-wireless@vger.kernel.org,
brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com,
megi@xff.cz, robh@kernel.org, efectn@protonmail.com,
krzk+dt@kernel.org, conor+dt@kernel.org, heiko@sntech.de,
nick@khadas.com, jagan@edgeble.ai, dsimic@manjaro.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] dt-bindings: net: wireless: brcm4329-fmac: add clock description.
Date: Mon, 24 Jun 2024 13:45:34 +0200 [thread overview]
Message-ID: <608b8673-a7d3-4a93-8719-841e451e7ddc@kernel.org> (raw)
In-Reply-To: <20240624081906.1399447-5-jacobe.zang@wesion.com>
On 24/06/2024 10:19, Jacobe Zang wrote:
> Add clocks and clock-names for brcm4329-fmac.
Which devices have this clock? All? You now mention driver, but this is
a binding so please describe hardware.
Subject: drop full stops. In every patch.
>
> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> ---
> .../bindings/net/wireless/brcm,bcm4329-fmac.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml b/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
> index e564f20d8f415..b9e39a62c3b32 100644
> --- a/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
> +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml
> @@ -121,6 +121,15 @@ properties:
> NVRAM. This would normally be filled in by the bootloader from platform
> configuration data.
>
> + clocks:
> + description: phandle to the clock connected on rtc clock line.
Drop redundant parts, like "phandle to the". Just use items with
description instead of above and maxItems.
> + maxItems: 1
> +
> + clock-names:
> + description: Names of the supplied clocks.
Drop description, completely redundant.
> + items:
> + - const: 32k
32k? That's the name of the clock? In the datasheet?
> +
> required:
> - compatible
> - reg
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-24 11:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 8:19 [PATCH v2 0/5] Add AP6275P wireless support Jacobe Zang
2024-06-24 8:19 ` [PATCH v2 1/5] arm64: dts: rockchip: Add AP6275P wireless support to Khadas Edge 2 Jacobe Zang
2024-06-24 11:52 ` Krzysztof Kozlowski
2024-06-25 8:04 ` Jacobe Zang
2024-07-01 8:41 ` Krzysztof Kozlowski
2024-06-24 8:19 ` [PATCH v2 2/5] net: wireless: brcmfmac: Add optional 32k clock enable support Jacobe Zang
2024-06-24 12:31 ` Kalle Valo
2024-06-24 8:19 ` [PATCH v2 3/5] net: wireless: brcmfmac: Add support for AP6275P Jacobe Zang
2024-06-24 8:19 ` [PATCH v2 4/5] dt-bindings: net: wireless: brcm4329-fmac: add clock description Jacobe Zang
2024-06-24 8:59 ` Arend van Spriel
2024-06-24 9:04 ` Jacobe Zang
2024-06-24 11:45 ` Krzysztof Kozlowski [this message]
2024-06-24 8:19 ` [PATCH v2 5/5] dt-bindings: net: wireless: brcm4329-fmac: add pci14e4,449d Jacobe Zang
2024-06-25 18:23 ` Arend Van Spriel
2024-06-26 6:28 ` Kalle Valo
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=608b8673-a7d3-4a93-8719-841e451e7ddc@kernel.org \
--to=krzk@kernel.org \
--cc=arend.vanspriel@broadcom.com \
--cc=bhelgaas@google.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=duoming@zju.edu.cn \
--cc=efectn@protonmail.com \
--cc=heiko@sntech.de \
--cc=jacobe.zang@wesion.com \
--cc=jagan@edgeble.ai \
--cc=krzk+dt@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=megi@xff.cz \
--cc=minipli@grsecurity.net \
--cc=nick@khadas.com \
--cc=robh@kernel.org \
/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).