From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jacobe Zang <jacobe.zang@wesion.com>,
"arend.vanspriel@broadcom.com" <arend.vanspriel@broadcom.com>
Cc: "kvalo@kernel.org" <kvalo@kernel.org>,
"duoming@zju.edu.cn" <duoming@zju.edu.cn>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"minipli@grsecurity.net" <minipli@grsecurity.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"brcm80211@lists.linux.dev" <brcm80211@lists.linux.dev>,
"brcm80211-dev-list.pdl@broadcom.com"
<brcm80211-dev-list.pdl@broadcom.com>,
"megi@xff.cz" <megi@xff.cz>, "robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"heiko@sntech.de" <heiko@sntech.de>, Nick Xie <nick@khadas.com>,
"efectn@protonmail.com" <efectn@protonmail.com>,
"jagan@edgeble.ai" <jagan@edgeble.ai>,
"dsimic@manjaro.org" <dsimic@manjaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 2/3] net: wireless: brcmfmac: Add optional 32k clock enable support
Date: Fri, 21 Jun 2024 12:06:01 +0200 [thread overview]
Message-ID: <6ad2a9ab-41a7-4560-8031-d5fa9f2cd558@kernel.org> (raw)
In-Reply-To: <TYZPR03MB7001C517C5BDC8967DECECD880C92@TYZPR03MB7001.apcprd03.prod.outlook.com>
On 21/06/2024 09:45, Jacobe Zang wrote:
>> That's DTS, not binding. I ask about Devicetree binding.
>
> Ok... I have grep in all dts files and can't find wifi node which is under pcie node has clock. So should I add an example in the yaml file?
No, that's example, not binding.
Validate your DTS with dtbs_check.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-06-21 10:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 2:00 [PATCH v1 0/3] Add AP6275P wireless support Jacobe Zang
2024-06-20 2:00 ` [PATCH v1 1/3] arm64: dts: rockchip: Add AP6275P wireless support to Khadas Edge 2 Jacobe Zang
2024-06-20 2:00 ` [PATCH v1 2/3] net: wireless: brcmfmac: Add optional 32k clock enable support Jacobe Zang
2024-06-20 6:22 ` Ondřej Jirman
2024-06-20 6:54 ` Krzysztof Kozlowski
2024-06-21 1:45 ` Jacobe Zang
2024-06-21 4:59 ` Arend Van Spriel
2024-06-21 6:03 ` Krzysztof Kozlowski
2024-06-21 7:45 ` Jacobe Zang
2024-06-21 10:06 ` Krzysztof Kozlowski [this message]
2024-06-20 2:00 ` [PATCH v1 3/3] net: wireless: brcmfmac: Add support for AP6275P Jacobe Zang
2024-06-22 0:22 ` Ondřej Jirman
2024-06-22 10:59 ` Arend van Spriel
2024-06-23 2:21 ` Jacobe Zang
2024-06-23 5:34 ` Arend Van Spriel
2024-06-23 8:01 ` Ondřej Jirman
2024-06-23 10:11 ` Jacobe Zang
2024-06-20 17:33 ` [PATCH v1 0/3] Add AP6275P wireless support Arend Van Spriel
2024-06-21 0:18 ` Jacobe Zang
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=6ad2a9ab-41a7-4560-8031-d5fa9f2cd558@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).