From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Stanimir Varbanov <svarbanov@mm-sol.com>,
linux-pci@vger.kernel.org, bhelgaas@google.com
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2] PCI: qcom: add missing supplies required for msm8996
Date: Wed, 14 Feb 2018 18:38:39 +0200 [thread overview]
Message-ID: <fe5639be-e520-b7f2-233e-c091440c77dc@linaro.org> (raw)
In-Reply-To: <d2b0f220-2982-dc86-ae9e-edf88e0b8e7d@linaro.org>
On 02/14/2018 06:14 PM, Srinivas Kandagatla wrote:
>
>
> On 14/02/18 16:00, Stanimir Varbanov wrote:
>>> .../devicetree/bindings/pci/qcom,pcie.txt | 4 ++++
>>> drivers/pci/dwc/pcie-qcom.c | 24
>>> ++++++++++++++++++++--
>>> 2 files changed, 26 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/pci/qcom,pcie.txt
>>> b/Documentation/devicetree/bindings/pci/qcom,pcie.txt
>>> index 3c9d321b3d3b..1fd703bd73e0 100644
>>> --- a/Documentation/devicetree/bindings/pci/qcom,pcie.txt
>>> +++ b/Documentation/devicetree/bindings/pci/qcom,pcie.txt
>>> @@ -189,6 +189,10 @@
>>> Value type: <phandle>
>>> Definition: A phandle to the analog power supply for IC which
>>> generates
>>> reference clock
>>> +- vddpe-3v3-supply:
>> shouldn't it be vddpe_3v3-supply to be aligned with the other supplies?
>>
> I noticed that, I had to do it intentionally
> As dt properties should follow - instead of _
I don't agree with that. If the supply name is more than one word it
should be separated by underscore ('git grep \-supply' in dts files).
--
regards,
Stan
prev parent reply other threads:[~2018-02-14 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 12:06 [PATCH v2] PCI: qcom: add missing supplies required for msm8996 srinivas.kandagatla
2018-02-14 16:00 ` Stanimir Varbanov
2018-02-14 16:14 ` Srinivas Kandagatla
2018-02-14 16:38 ` Stanimir Varbanov [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=fe5639be-e520-b7f2-233e-c091440c77dc@linaro.org \
--to=stanimir.varbanov@linaro.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=svarbanov@mm-sol.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).