On Fri, Apr 15, 2016 at 10:39 AM, Laxman Dewangan <ldewangan@xxxxxxxxxx> wrote:
On Friday 15 April 2016 01:38 PM, Linus Walleij wrote:Well in a comment to the previous patch you just said that the
On Tue, Apr 12, 2016 at 4:56 PM, Laxman Dewangan <ldewangan@xxxxxxxxxx>Yes, I looked for the common property but did not found anything near to
wrote:
+static const struct pinconf_generic_params tegra_io_pads_cfg_params[] =What's so nvidia-specific about this?
{
+ {
+ .property = "nvidia,io-rail-voltage",
+ .param = TEGRA_IO_RAIL_VOLTAGE,
+ }, {
We have power-source in
Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt
which takes a custom argument. This is obviously what you
are doing (selecting one of two rails), so use that binding.
this.
My understating for power-source is that selecting the source of supply, not
the voltages.
hardware actually does not regulate voltages. Isn't the actual case
that there are two rails with two different voltages, and you select one
of the rails for the pin?
That is not really selecting a voltage, that is selecting a power
rail.
I am looking something power-source-voltage-level.If the pin could actually set a voltage level it would have a regulator.
Should we add this?
I don't believe that. I think it is selecting one of two rails which
could theoretically hold two totally different voltages.
And that is what power-source is about.