From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, bhupesh.linux@gmail.com,
lorenzo.pieralisi@arm.com, agross@kernel.org,
svarbanov@mm-sol.com, bhelgaas@google.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
sboyd@kernel.org, mturquette@baylibre.com,
linux-clk@vger.kernel.org, Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v3 7/7] arm64: dts: qcom: sa8155: Enable PCIe nodes
Date: Tue, 8 Mar 2022 16:31:46 -0600 [thread overview]
Message-ID: <YifZUtH8hbelcB8L@builder.lan> (raw)
In-Reply-To: <CAH=2Ntz2=pgysEVSfSuGd12C-Am-qRZymaotCw-Lwp0_xaNcOg@mail.gmail.com>
On Thu 03 Mar 00:09 CST 2022, Bhupesh Sharma wrote:
> Hi Dmitry,
>
> On Thu, 3 Mar 2022 at 02:29, Dmitry Baryshkov
> <dmitry.baryshkov@linaro.org> wrote:
> >
> > On Wed, 2 Mar 2022 at 23:31, Bhupesh Sharma <bhupesh.sharma@linaro.org> wrote:
> > >
> > > SA8155p ADP board supports the PCIe0 controller in the RC
> > > mode (only). So add the support for the same.
> > >
> > > Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> > > Cc: Vinod Koul <vkoul@kernel.org>
> > > Cc: Rob Herring <robh+dt@kernel.org>
> > > Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
> > > ---
> > > arch/arm64/boot/dts/qcom/sa8155p-adp.dts | 42 ++++++++++++++++++++++++
> > > 1 file changed, 42 insertions(+)
> > >
> > > diff --git a/arch/arm64/boot/dts/qcom/sa8155p-adp.dts b/arch/arm64/boot/dts/qcom/sa8155p-adp.dts
> > > index 8756c2b25c7e..3f6b3ee404f5 100644
> > > --- a/arch/arm64/boot/dts/qcom/sa8155p-adp.dts
> > > +++ b/arch/arm64/boot/dts/qcom/sa8155p-adp.dts
> > > @@ -387,9 +387,51 @@ &usb_2_qmpphy {
> > > vdda-pll-supply = <&vdda_usb_ss_dp_core_1>;
> > > };
> > >
> > > +&pcie0 {
> > > + status = "okay";
> > > +};
> > > +
> > > +&pcie0_phy {
> > > + status = "okay";
> > > + vdda-phy-supply = <&vreg_l18c_0p88>;
> > > + vdda-pll-supply = <&vreg_l8c_1p2>;
> > > +};
> > > +
> > > +&pcie1_phy {
> > > + vdda-phy-supply = <&vreg_l18c_0p88>;
> > > + vdda-pll-supply = <&vreg_l8c_1p2>;
> > > +};
> > > +
> > > &tlmm {
> > > gpio-reserved-ranges = <0 4>;
> > >
> > > + bt_en_default: bt_en_default {
'_' is not a valid character in the node name (it is in the label).
> > > + mux {
Please flatten this, you can omit the mux and config subnodes and put
the properties directly in the state node.
> > > + pins = "gpio172";
> > > + function = "gpio";
> > > + };
> > > +
> > > + config {
> > > + pins = "gpio172";
> > > + drive-strength = <2>;
> > > + bias-pull-down;
> > > + };
> > > + };
> > > +
> > > + wlan_en_default: wlan_en_default {
> > > + mux {
> > > + pins = "gpio169";
> > > + function = "gpio";
> > > + };
> > > +
> > > + config {
> > > + pins = "gpio169";
> > > + drive-strength = <16>;
> > > + output-high;
> > > + bias-pull-up;
> > > + };
> > > + };
> > > +
> >
> > Not related to PCIe
>
> Hmm.. I have no strong personal opinion on this, so let's see what
> Bjorn thinks about the same.
> My reasoning for keeping it here was to just capture that we have
> 'bt_en' and 'wlan_en' related tlmm details here, so that when you send
> out the reworked QCAxxxx mfd series (see [1]) later, I can easily plug
> it in for SA8155p ADP dts as well with the 'bt' and 'wlan' constructs.
>
The BT_EN is unrelated to PCIe, and I'm not able to see where you select
the wlan_en_default state, so this would be dangling.
So the bt_en should come in a patch together with a bluetooth node and
the wlan_en_default should come with something that ensures that the
WiFi portion of the chip is powered and the gpio enabled.
Regards,
Bjorn
> [1]. https://lore.kernel.org/lkml/20210621223141.1638189-2-dmitry.baryshkov@linaro.org/T/
>
> Regards.
> Bhupesh
>
> > > usb2phy_ac_en1_default: usb2phy_ac_en1_default {
> > > mux {
> > > pins = "gpio113";
> > > --
> > > 2.35.1
> > >
> >
> >
> > --
> > With best wishes
> > Dmitry
prev parent reply other threads:[~2022-03-08 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 20:30 [PATCH v3 0/7] Add PCIe support for SM8150 SoC Bhupesh Sharma
2022-03-02 20:30 ` [PATCH v3 1/7] dt-bindings: pci: qcom: Document PCIe bindings " Bhupesh Sharma
2022-03-02 20:30 ` [PATCH v3 2/7] dt-bindings: phy: qcom,qmp: Add SM8150 PCIe PHY bindings Bhupesh Sharma
2022-03-02 20:30 ` [PATCH v3 3/7] clk: qcom: gcc: Add PCIe0 and PCIe1 GDSC for SM8150 Bhupesh Sharma
2022-03-02 20:30 ` [PATCH v3 4/7] phy: qcom-qmp: Add SM8150 PCIe QMP PHYs Bhupesh Sharma
2022-03-02 20:30 ` [PATCH v3 5/7] PCI: qcom: Add SM8150 SoC support Bhupesh Sharma
2022-03-24 20:52 ` Rob Herring
2022-03-02 20:30 ` [PATCH v3 6/7] arm64: dts: qcom: sm8150: Add PCIe nodes Bhupesh Sharma
2022-03-02 20:30 ` [PATCH v3 7/7] arm64: dts: qcom: sa8155: Enable " Bhupesh Sharma
2022-03-02 20:59 ` Dmitry Baryshkov
2022-03-03 6:09 ` Bhupesh Sharma
2022-03-08 22:31 ` Bjorn Andersson [this message]
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=YifZUtH8hbelcB8L@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=svarbanov@mm-sol.com \
--cc=vkoul@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).