From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: agross@kernel.org, bjorn.andersson@linaro.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:43:33 +0100 [thread overview]
Message-ID: <3a5b24b9-a63f-ec24-e0b0-3a44e9583207@linaro.org> (raw)
In-Reply-To: <Yl8La/pFbQJNUQTy@gerhold.net>
On 19/04/2022 20:20, Stephan Gerhold wrote:
> On Tue, Apr 19, 2022 at 02:09:02AM +0100, Bryan O'Donoghue wrote:
>> +&otg {
>> + status = "okay";
>> + usb-role-switch;
>> +
>> + pinctrl-names = "default", "host", "device";
>> + pinctrl-0 = <&pinctrl_otg_default>;
>> + pinctrl-1 = <&pinctrl_otg_host>;
>> + pinctrl-2 = <&pinctrl_otg_device>;
>> + pin-switch-delay-us = <100000>;
>> +
>> + ulpi {
>> + usb_hs_phy: phy {
>> + qcom,enable-vbus-pullup;
>
> Hm, what handles the USB detection on this port? The tps6598x?
tps yes
> Can it provide an extcon so that you don't need to keep the USB PHY
> powered permanently?
Per my understanding new extcon is verboten
This particular hardware has an internal USB hub intermediating to
switch-in internal USB peripherals when disconnected from the external
type-c port so, we actually don't want to switch off the PHY.
>
>> + [...]
>> +&pronto {
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&wcnss_pin_a &wcnss_pin_antennae>;
>> + status = "okay";
>> +
>> + iris {
>> + compatible = "qcom,wcn3680";
>> + };
>> +
>> + smd-edge {
>> + wcnss {
>> + bt {
>> + local-bd-address = [ 55 44 33 22 11 00 ];
>
> Is this really needed?
>
> The DB410c LK and U-Boot port (and also lk2nd) automatically generate a
> WiFi/BT address based on the eMMC serial number. That's probably a
> better solution than a fixed MAC address specified here.
Ah yes I remember seeing the strings being populated.
Thanks, I'll zap this.
---
bod
next prev parent reply other threads:[~2022-04-19 21:43 UTC|newest]
Thread overview: 32+ 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 18:31 ` Stephan Gerhold
2022-04-20 10:12 ` Jun Nie
2022-04-19 21:11 ` Bjorn Andersson
2022-04-20 5:34 ` Stephan Gerhold
[not found] ` <bc6ce23672c52b1f2593fcac720edf9ca9e9fdaa.camel@mailoo.org>
2022-04-19 22:01 ` Bryan O'Donoghue
2022-05-26 13:32 ` Bryan O'Donoghue
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 [this message]
2022-04-19 21:39 ` Bjorn Andersson
2022-04-19 21:52 ` Bryan O'Donoghue
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=3a5b24b9-a63f-ec24-e0b0-3a44e9583207@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=stephan@gerhold.net \
--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).