From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: 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] PCI: qcom: add missing supplies required for msm8996
Date: Tue, 23 Jan 2018 10:33:13 +0000 [thread overview]
Message-ID: <5f43164a-4d84-12be-7f69-f7bbaaf1d64c@linaro.org> (raw)
In-Reply-To: <1a3cc92e-545e-a703-7130-6a9c58854e03@mm-sol.com>
On 23/01/18 10:14, Stanimir Varbanov wrote:
> Hi,
>
> On 01/23/2018 11:46 AM, Srinivas Kandagatla wrote:
>>
>>
>> On 23/01/18 09:23, Stanimir Varbanov wrote:
>>> Hey Srini,
>>>
>>> As there are no comments I'd propose to change the endpoint supplies to
>>> more generic names.
>>>
>> Sure, I will respin this with your suggestions, except the 3v3 and 1v5
>> suffix due to the reasons below:
>>>> +- vdda-1p8-supply:
>>>> + Usage: required for msm8996
>>>> + Value type: <phandle>
>>>> + Definition: A phandle to the 1.8v analog power supply
>>>> +
>>>
>>> This should be dropped, because it is part of the phy.
>> Yep.
>>
>>>
>>>> - vdda_phy-supply:
>>>> Usage: required for ipq/apq8064
>>>> Value type: <phandle>
>>>> @@ -189,6 +194,15 @@
>>>> Value type: <phandle>
>>>> Definition: A phandle to the analog power supply for IC which
>>>> generates
>>>> reference clock
>>>> +- vddpe-supply:
>>>> + Usage: optional
>>>> + Value type: <phandle>
>>>> + Definition: A phandle to the PCIe endpoint power supply
>>>
>>> vddpe_3v3-supply
>> Why do we need suffix here? AFAIU, It does not add any value, instead it
>> would confuse the users.
>
> vddpe and vddpe1 is already confusing as well.
I partly agree with you.
How would you represent if there are two power 3v3 supplies for the
endpoint?
>
> Lets imagine that powering up the endpointX needs some specific sequence
> between 3v3 and 1v5 and endpointY (which could be connected on the same
> PCIe lane) has different power sequence, how we would handle that in the
> qcom pcie host driver?
power sequencing is all together a different issue, that is not
addressed in this patch. Am hoping that this will be fixed as part of
making pwrseq interface more generic. Not sure where it endedup now!!
--srini
>
>>
>> These are power supplies for endpoint which could be of any voltage. In
>
> I don't think that could be any values see PCIe mini card
> electromechanical specification. There on the connector are provided 3v3
> and 1v5.
>
>> this case both endpoint supplies are 3v3, these could be 1.8 or 5v or
>> 12v in some other cases.
>
> If we see hw designs with 5v and 12v we could extend the binding and the
> driver with support for them. I want to be exact in the names and
> voltages in the driver and bindings.
>
prev parent reply other threads:[~2018-01-23 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 9:20 srinivas.kandagatla
2017-12-12 20:17 ` Rob Herring
2017-12-14 10:06 ` Stanimir Varbanov
2017-12-14 11:19 ` Srinivas Kandagatla
2018-01-23 9:23 ` Stanimir Varbanov
2018-01-23 9:46 ` Srinivas Kandagatla
2018-01-23 10:14 ` Stanimir Varbanov
2018-01-23 10:33 ` 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=5f43164a-4d84-12be-7f69-f7bbaaf1d64c@linaro.org \
--to=srinivas.kandagatla@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=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
all inboxes | Powered by JetHome®