devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: agross@kernel.org, robh+dt@kernel.org, krzk+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	shawn.guo@linaro.org, jun.nie@linaro.org, benl@squareup.com,
	jwillcox@squareup.com, jgates@squareup.com, mchen@squareup.com,
	zac@squareup.com, Leo Yan <leo.yan@linaro.org>
Subject: Re: [PATCH v1 3/4] arm64: dts: Add aqp8039-t2 board
Date: Tue, 19 Apr 2022 22:52:28 +0100	[thread overview]
Message-ID: <0574491c-1b32-a6c8-d8ad-7c4c5c4662b2@linaro.org> (raw)
In-Reply-To: <Yl8r/c0psJTGhEEA@builder.lan>

On 19/04/2022 22:39, Bjorn Andersson wrote:
> On Mon 18 Apr 20:09 CDT 2022, Bryan O'Donoghue wrote:
>> +	wcnss_pin_antennae: wcnss_pin_antennae {
>> +		pinmux {
>> +			pins = "gpio1", "gpio2";
>> +		};
>> +		pinconf {
>> +			pins = "gpio1", "gpio2";
>> +			function = PMIC_GPIO_FUNC_NORMAL;
>> +			output-high;
> 
> Could it be that gpio1 and 2 control two power supplies for two antennas
> and that this should have been represented as regulators instead?

Those are the GPIOs responsible for switching between antenna

Off-topic:
When doing antenna diversity switching the WCNSS firmware owns these two 
GPIOs.

The rough algorithm is
for (i = 0; i < 2; i++)
- Switch GPIO[i]
- Send a probe to the WiFi AP
- Wait for a response
- Measure the RSSI

Then decide which antenna has the better signal strength. So actually 
WCNSS owns these two pins.

I have an evil plan to implement ieee80211_ops::get_antenna() in the future.

In theory all we have to do is read the GPIOs inside the callback.

>> +		pm8916_l6: l6 {
>> +			regulator-min-microvolt = <1800000>;
>> +			regulator-max-microvolt = <1800000>;
>> +			regulator-always-on; /* copy from v3.10 */
> 
> Can you do better than "copy from v3.10"?

Sure. I'll put in a comment why.

---
bod


  reply	other threads:[~2022-04-19 21:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  1:08 [PATCH v1 0/4] Add MSM8939 SoC support with two devices Bryan O'Donoghue
2022-04-19  1:09 ` [PATCH v1 1/4] dt-bindings: arm: qcom: Document MSM8939 SoC binding Bryan O'Donoghue
2022-04-19  7:13   ` Krzysztof Kozlowski
2022-04-19 12:12   ` Rob Herring
2022-04-19  1:09 ` [PATCH v1 2/4] arm64: dts: Add msm8939 SoC Bryan O'Donoghue
2022-04-19  7:33   ` Krzysztof Kozlowski
2022-04-19  8:30     ` Bryan O'Donoghue
2022-04-19  8:44       ` Krzysztof Kozlowski
2022-04-20  9:31     ` Jun Nie
2022-04-20  9:38       ` Krzysztof Kozlowski
2022-04-20  9:57         ` Jun Nie
2022-04-20 10:00           ` Jun Nie
2022-04-20 10:10             ` Krzysztof Kozlowski
2022-04-20 10:09           ` Krzysztof Kozlowski
2022-04-19 17:21   ` Vincent Knecht
2022-04-19 22:01     ` Bryan O'Donoghue
2022-05-26 13:32     ` Bryan O'Donoghue
2022-04-19 18:31   ` Stephan Gerhold
2022-04-20 10:12     ` Jun Nie
2022-04-19 18:47   ` Vincent Knecht
2022-04-19 21:11   ` Bjorn Andersson
2022-04-20  5:34     ` Stephan Gerhold
2022-04-19  1:09 ` [PATCH v1 3/4] arm64: dts: Add aqp8039-t2 board Bryan O'Donoghue
2022-04-19  7:35   ` Krzysztof Kozlowski
2022-04-19 19:20   ` Stephan Gerhold
2022-04-19 21:43     ` Bryan O'Donoghue
2022-04-19 21:39   ` Bjorn Andersson
2022-04-19 21:52     ` Bryan O'Donoghue [this message]
2022-04-19  1:09 ` [PATCH v1 4/4] arm64: dts: Add msm8939 Sony Xperia M4 Aqua Bryan O'Donoghue
2022-04-19 19:27   ` Stephan Gerhold
2022-04-19 22:03     ` Bryan O'Donoghue
2022-04-20  5:36       ` Stephan Gerhold
2022-05-26 22:03       ` Dmitry Baryshkov
2022-04-19 21:51   ` Bjorn Andersson

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=0574491c-1b32-a6c8-d8ad-7c4c5c4662b2@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=agross@kernel.org \
    --cc=benl@squareup.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jgates@squareup.com \
    --cc=jun.nie@linaro.org \
    --cc=jwillcox@squareup.com \
    --cc=krzk+dt@kernel.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mchen@squareup.com \
    --cc=robh+dt@kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=zac@squareup.com \
    /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).