ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bhagavathi Perumal S <bperumal@codeaurora.org>
To: ath10k@lists.infradead.org
Subject: Re: [PATCH v4 2/3] dt-bindings: net: ath10k: add new dt entry to identify external FEM
Date: Wed, 12 Dec 2018 10:10:12 +0530	[thread overview]
Message-ID: <ec3d96f934f8bb956af6115c94316195@codeaurora.org> (raw)
In-Reply-To: <5dd13e00175645e495df16858399d678@euamsexm01f.eu.qualcomm.com>

On 2018-12-12 10:00, Bhagavathi Perumal S wrote:
> -----Original Message-----
> From: ath10k <ath10k-bounces@lists.infradead.org> On Behalf Of
> Sebastian Gottschall
> Sent: Wednesday, December 12, 2018 1:38 AM
> To: ath10k@lists.infradead.org
> Subject: [EXTERNAL] Re: [PATCH v4 2/3] dt-bindings: net: ath10k: add
> new dt entry to identify external FEM
> 
> documentation still wrong. only  microsemi-lx5586 is valid .all other
> values are invalid see patch 4
> 
> +	if (!strcmp("microsemi-lx5586", fem_name)) {
> +		bb_timing->bb_tx_timing = 0x00;
> +		bb_timing->bb_xpa_timing = 0x0101;
> +	} else {
> +		return -ENOENT;
> +	}
> 

Thanks, Missed it. Need to allow other FEM devices to use default values 
with warning message. Will change it.

> Am 11.12.2018 um 17:13 schrieb Bhagavathi Perumal S:
>> 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.
>> 
>> Signed-off-by: Bhagavathi Perumal S <bperumal@codeaurora.org>
>> ---
>>   Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt | 9 
>> ++++++++-
>>   1 file changed, 8 insertions(+), 1 deletion(-)
>> 
>> diff --git
>> a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> index ef60f25..71530fd 100644
>> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
>> @@ -61,8 +61,14 @@ Optional properties:
>>   	Value type: <phandle>
>>   	Definition: reference to the reserved-memory for the msa region
>>   		    used by the wifi firmware running in Q6.
>> +- ext-fem-name:
>> +	Usage: Optional
>> +	Value type: string
>> +	Definition: Name of external front end module used. Some valid FEM 
>> names
>> +		    for example: "microsemi-lx5586", "sky85703-11"
>> +		    and "sky85803" etc.
>> 
>> -Example (to supply the calibration data alone):
>> +Example (to supply PCI based wifi block details):
>> 
>>   In this example, the node is defined as child node of the PCI 
>> controller.
>> 
>> @@ -77,6 +83,7 @@ pci {
>>   		wifi@0,0 {
>>   			reg = <0 0 0 0 0>;
>>   			qcom,ath10k-calibration-data = [ 01 02 03 ... ];
>> +			ext-fem-name = "microsemi-lx5586";
>>   		};
>>   	};
>>   };
> 
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2018-12-12  4:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 16:13 [PATCH v4 0/3] ath10k: Add support to configure BB timing for external FEM Bhagavathi Perumal S
2018-12-11 16:13 ` [PATCH v4 1/3] dt-bindings: net: ath10k: fix node name and device type in qcom ath10k example Bhagavathi Perumal S
2018-12-17 21:44   ` Rob Herring
2018-12-20 17:10   ` Kalle Valo
2018-12-11 16:13 ` [PATCH v4 2/3] dt-bindings: net: ath10k: add new dt entry to identify external FEM Bhagavathi Perumal S
2018-12-11 20:07   ` Sebastian Gottschall
     [not found]     ` <5dd13e00175645e495df16858399d678@euamsexm01f.eu.qualcomm.com>
2018-12-12  4:40       ` Bhagavathi Perumal S [this message]
2018-12-12  5:52         ` Bhagavathi Perumal S
2018-12-13  9:08     ` Kalle Valo
2018-12-17 20:37   ` Rob Herring
2018-12-20 13:23     ` Kalle Valo
2018-12-11 16:13 ` [PATCH v4 3/3] 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=ec3d96f934f8bb956af6115c94316195@codeaurora.org \
    --to=bperumal@codeaurora.org \
    --cc=ath10k@lists.infradead.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