From: Rob Herring <robh@kernel.org>
To: Anilkumar Kolli <akolli@codeaurora.org>
Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATH v3 1/2] dt: bindings: add new DT entry for ath11k PCI device support
Date: Thu, 18 Nov 2021 17:11:47 -0600 [thread overview]
Message-ID: <YZbds1DgmwbFPQdM@robh.at.kernel.org> (raw)
In-Reply-To: <1637244892-27267-1-git-send-email-akolli@codeaurora.org>
On Thu, Nov 18, 2021 at 07:44:51PM +0530, Anilkumar Kolli wrote:
> Ath11k driver supports PCI devices such as QCN9074/QCA6390.
> Ath11k firmware uses host DDR memory, DT entry is used to reserve
> these host DDR memory regions, send these memory base
> addresses using DT entries.
>
> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org>
> ---
> V2:
> - Use reserved-memory (Rob)
>
> .../bindings/net/wireless/qcom,ath11k.yaml | 48 ++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
> index 85c2f699d602..5a8994f6cb10 100644
> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k.yaml
> @@ -150,6 +150,12 @@ properties:
> string to uniquely identify variant of the calibration data in the
> board-2.bin for designs with colliding bus and device specific ids
>
> + memory-region:
> + maxItems: 1
> + description:
> + phandle to a node describing reserved memory (System RAM memory)
> + used by ath11k firmware (see bindings/reserved-memory/reserved-memory.txt)
> +
> required:
> - compatible
> - reg
> @@ -279,3 +285,45 @@ examples:
> "tcl2host-status-ring";
> qcom,rproc = <&q6v5_wcss>;
> };
> +
This looks like a separate example. Please split to its own entry.
> + memory {
> + device_type = "memory";
> + reg = <0x0 0x40000000 0x0 0x20000000>;
> + };
Outside the scope of what's needed in the example.
> +
> + reserved-memory {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> +
> + qcn9074_pcie0: qcn9074_pcie0@51100000 {
> + no-map;
> + reg = <0x0 0x51100000 0x0 0x03500000>;
> + };
> +
> + qcn9074_pcie1: qcn9074_pcie1@54600000 {
> + no-map;
> + reg = <0x0 0x54600000 0x0 0x03500000>;
> + };
> + };
As is this really.
> +
> + pcie0_rp: pcie0_rp {
> + reg = <0 0 0 0 0>;
This isn't a valid PCI bus binding.
> +
> + status = "ok";
Don't need status.
> + ath11k_0: ath11k@0 {
wifi@0
> + reg = <0 0 0 0 0 >;
> + memory-region = <&qcn9074_pcie0>;
> + };
> + };
> +
> + pcie1_rp: pcie1_rp {
> + reg = <0 0 0 0 0>;
> +
> + status = "ok";
> + ath11k_1: ath11k@1 {
> + reg = <0 0 0 0 0 >;
unit-address and reg don't match.
Why do we need 2 nodes in the first place?
> + memory-region = <&qcn9074_pcie1>;
> + };
> + };
> +
> --
> 2.7.4
>
>
next prev parent reply other threads:[~2021-11-18 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 14:14 [PATH v3 1/2] dt: bindings: add new DT entry for ath11k PCI device support Anilkumar Kolli
2021-11-18 14:14 ` [PATH v3 2/2] ath11k: Use reserved host DDR addresses from DT for PCI devices Anilkumar Kolli
2021-11-19 13:00 ` Kalle Valo
2021-11-19 13:56 ` Sven Eckelmann
2021-11-18 22:09 ` [PATH v3 1/2] dt: bindings: add new DT entry for ath11k PCI device support Rob Herring
2021-11-19 8:21 ` Anilkumar Kolli
2021-11-18 23:11 ` Rob Herring [this message]
2021-11-19 8:41 ` Anilkumar Kolli
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=YZbds1DgmwbFPQdM@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=akolli@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-wireless@vger.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).