From: Rob Herring <robh@kernel.org>
To: Bhagavathi Perumal S <bperumal@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt: bindings: add new dt entry to indentify external FEM
Date: Mon, 15 Oct 2018 14:24:25 -0500 [thread overview]
Message-ID: <20181015192425.GA19699@bogus> (raw)
In-Reply-To: <1538653364-1239-2-git-send-email-bperumal@codeaurora.org>
On Thu, Oct 04, 2018 at 05:12:43PM +0530, Bhagavathi Perumal S wrote:
> This adds new dt entry ext-fem-name, it is used by ath10k driver
> to select correct timing parameters and configure it in target wifi hardware.
> The Front End Module(FEM) normally includes tx power amplifier(PA) and
> rx low noise amplifier(LNA). The default timing parameters like tx end to
> PA off timing values were fine tuned for internal FEM used in reference
> design. And these timing values can not be same if ODM modifies hardware
> design with different external FEM. This DT entry helps to choose correct
> timing values in driver if different external FEM hardware used.
'dt-bindings: net: ath10k: ...' for the subject please.
>
> Signed-off-by: Bhagavathi Perumal S <bperumal@codeaurora.org>
> ---
> .../bindings/net/wireless/qcom,ath10k.txt | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
> index 7fd4e8c..fbaf309 100644
> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
> @@ -56,6 +56,7 @@ Optional properties:
> the length can vary between hw versions.
> - <supply-name>-supply: handle to the regulator device tree node
> optional "supply-name" is "vdd-0.8-cx-mx".
> +- ext-fem-name: name of external front end module used.
What are valid names? What if the OS doesn't recognize the name? Perhaps
this should be a compatible string for the particular module instead?
Then it could cover any differences, not just the FEM.
>
> Example (to supply the calibration data alone):
>
> @@ -150,3 +151,24 @@ wifi@18000000 {
> <0 141 0 /* CE11 */ >;
> vdd-0.8-cx-mx-supply = <&pm8998_l5>;
> };
> +
> +Example (to supply the external front end module name):
> +
> +In this example, the front end module is defined as a property of the ath10k
> +device node.
Really need a whole new example for 1 property?
> +
> +pci {
> + pcie@0 {
> + reg = <0 0 0 0 0>;
> + #interrupt-cells = <1>;
> + #size-cells = <2>;
> + #address-cells = <3>;
> + device_type = "pci";
> +
> + ath10k@0,0 {
wifi@0,0
> + reg = <0 0 0 0 0>;
> + device_type = "pci";
> + ext-fem-name = "microsemi-lx5586";
> + };
> + };
> +};
> --
> 1.9.1
>
next prev parent reply other threads:[~2018-10-15 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 11:42 [PATCH 0/2] ath10k: Add support to configure BB timing for external FEM Bhagavathi Perumal S
2018-10-04 11:42 ` [PATCH 1/2] dt: bindings: add new dt entry to indentify " Bhagavathi Perumal S
2018-10-15 19:24 ` Rob Herring [this message]
2018-10-30 8:41 ` bperumal
2018-10-30 15:32 ` Rob Herring
2018-11-07 10:47 ` Bhagavathi Perumal S
2018-10-04 11:42 ` [PATCH 2/2] ath10k: Add support to configure BB timing over wmi Bhagavathi Perumal S
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=20181015192425.GA19699@bogus \
--to=robh@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=bperumal@codeaurora.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).