From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: andy.gross@linaro.org, linux-arm-msm@vger.kernel.org,
david.brown@linaro.org, robh+dt@kernel.org,
linux-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: db600c: add support to pcie refclk
Date: Wed, 21 Mar 2018 13:26:19 +0800 [thread overview]
Message-ID: <831e8c3b-06e1-8653-df0b-2c1de05834be@linaro.org> (raw)
In-Reply-To: <20180321033518.GB1403@tuxbook-pro>
Thanks Bjorn for the review comments,
On 21/03/18 11:35, Bjorn Andersson wrote:
> On Tue 20 Mar 17:28 HKT 2018, Srinivas Kandagatla wrote:
>
>> From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>>
>> This patch adds support to external pcie refclk.
>>
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>> ---
>> arch/arm/boot/dts/qcom-apq8064-db600c.dts | 27 +++++++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/qcom-apq8064-db600c.dts b/arch/arm/boot/dts/qcom-apq8064-db600c.dts
>> index 50151ef6e912..7587088c122f 100644
>> --- a/arch/arm/boot/dts/qcom-apq8064-db600c.dts
>> +++ b/arch/arm/boot/dts/qcom-apq8064-db600c.dts
>> @@ -45,6 +45,18 @@
>>
>> };
>>
>> + clocks {
>> + compatible = "simple-bus";
>> + pcie_refclk: pcie-refclk {
>
> As the si53154 is used to acquire 3 different clocks (2 pcie and 1 sata)
> it would be nice to accurately represent this in the DT. That said,
> exposing this as a clock allow us to change the representation here
> later. (Both pcie_core_clk and pcie_eth_clk use the same gpio pin as
> enable pin, so I don't know how to represent this...)
>
This is a refclk, which should be always same for both PCIe Controllers
and connected PCIe endpoints.
For sata we should have one more refclk entry of its own.
> So for now, please name this "pcie_core_clk", per the schematics.
This is pcie refclk, if you follow the line in the schematics should see
that it terminates to pcie refclk.
>
>> + pinctrl-0 = <&pcie_pins>;
>> + pinctrl-names = "default";
>> + compatible = "gpio-gate-clock";
>> + clocks = <&rpmcc 27>;
>> + #clock-cells = <0>;
>> + enable-gpios = <&pm8921_gpio 22 GPIO_ACTIVE_HIGH>;
>> + };
>> + };
>> +
>> hdmi-out {
>> compatible = "hdmi-connector";
>> type = "a";
>> @@ -140,6 +152,16 @@
>>
>> qcom,ssbi@500000 {
>> pmic@0 {
>> + gpio@150 {
>> + pcie_pins: pcie_pins {
>
> Please label this "pcie_clk_en_pin" and don't use '_' in the name of the
> node.
>
I agree, Will fix it.
>> + pios {
>
> You can omit this level and just put the properties in directly in the
> pcie-clk-en node.
Okay.
thanks,
srini
>
>> + pins = "gpio22";
>> + function = "normal";
>> + power-source = <PM8921_GPIO_VPH>;
>> + };
>> + };
>> + };
>> +
>
> Regards,
> Bjorn
>
prev parent reply other threads:[~2018-03-21 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 9:28 [PATCH] ARM: dts: db600c: add support to pcie refclk srinivas.kandagatla
2018-03-21 3:35 ` Bjorn Andersson
2018-03-21 5:26 ` Srinivas Kandagatla [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=831e8c3b-06e1-8653-df0b-2c1de05834be@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=robh+dt@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).