From: Jon Hunter <jonathanh@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
thierry.reding@gmail.com, airlied@linux.ie,
swarren@wwwdotorg.org, gnurou@gmail.com
Cc: dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage
Date: Sun, 8 May 2016 13:13:56 +0100 [thread overview]
Message-ID: <572F2D84.3060505@nvidia.com> (raw)
In-Reply-To: <572CB906.3090004@nvidia.com>
On 06/05/16 16:32, Laxman Dewangan wrote:
>
> On Friday 06 May 2016 08:07 PM, Jon Hunter wrote:
>> On 06/05/16 11:45, Laxman Dewangan wrote:
>> +
>> + /* Last entry */
>> + TEGRA_IO_PAD_MAX,
>> Nit should these be TEGRA_IO_PADS_xxx?
>
> Because this was name of single pad and hence I said TEGRA_IO_PAD_XXX.
Aren't these used to set the voltage level and power state for the
entire group of IOs? Confused :-(
>>> +};
>>> +
>>> +/* tegra_io_pads_source_voltage: The voltage level of IO rails which
>>> source
>>> + * the IO pads.
>>> + */
>>> +enum tegra_io_pads_source_voltage {
>>> + TEGRA_IO_PADS_SOURCE_VOLTAGE_1800000UV,
>>> + TEGRA_IO_PADS_SOURCE_VOLTAGE_3300000UV,
>>> +};
>> Nit I wonder if we can make this shorter ...
>>
>> enum tegra_io_pads_vconf {
>> TEGRA_IO_PADS_VCONF_1V8,
>> TEGRA_IO_PADS_VCONF_3V3,
>
> This looks good but for voltage and current, unit is used uV/uV across
> the system. So wanted to have same unit.
Now it is an enum does it matter? Or maybe just have ...
enum tegra_io_pads_vconf {
TEGRA_IO_PADS_1800000UV,
TEGRA_IO_PADS_3300000UV,
};
Cheers
Jon
WARNING: multiple messages have this Message-ID (diff)
From: Jon Hunter <jonathanh@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
<thierry.reding@gmail.com>, <airlied@linux.ie>,
<swarren@wwwdotorg.org>, <gnurou@gmail.com>
Cc: <dri-devel@lists.freedesktop.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V4 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage
Date: Sun, 8 May 2016 13:13:56 +0100 [thread overview]
Message-ID: <572F2D84.3060505@nvidia.com> (raw)
In-Reply-To: <572CB906.3090004@nvidia.com>
On 06/05/16 16:32, Laxman Dewangan wrote:
>
> On Friday 06 May 2016 08:07 PM, Jon Hunter wrote:
>> On 06/05/16 11:45, Laxman Dewangan wrote:
>> +
>> + /* Last entry */
>> + TEGRA_IO_PAD_MAX,
>> Nit should these be TEGRA_IO_PADS_xxx?
>
> Because this was name of single pad and hence I said TEGRA_IO_PAD_XXX.
Aren't these used to set the voltage level and power state for the
entire group of IOs? Confused :-(
>>> +};
>>> +
>>> +/* tegra_io_pads_source_voltage: The voltage level of IO rails which
>>> source
>>> + * the IO pads.
>>> + */
>>> +enum tegra_io_pads_source_voltage {
>>> + TEGRA_IO_PADS_SOURCE_VOLTAGE_1800000UV,
>>> + TEGRA_IO_PADS_SOURCE_VOLTAGE_3300000UV,
>>> +};
>> Nit I wonder if we can make this shorter ...
>>
>> enum tegra_io_pads_vconf {
>> TEGRA_IO_PADS_VCONF_1V8,
>> TEGRA_IO_PADS_VCONF_3V3,
>
> This looks good but for voltage and current, unit is used uV/uV across
> the system. So wanted to have same unit.
Now it is an enum does it matter? Or maybe just have ...
enum tegra_io_pads_vconf {
TEGRA_IO_PADS_1800000UV,
TEGRA_IO_PADS_3300000UV,
};
Cheers
Jon
next prev parent reply other threads:[~2016-05-08 12:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 10:45 [PATCH V4 0/3] soc/tegra: Add support for IO pads power and voltage control Laxman Dewangan
2016-05-06 10:45 ` Laxman Dewangan
2016-05-06 10:45 ` [PATCH V4 1/3] soc/tegra: pmc: Use BIT macro for register field definition Laxman Dewangan
2016-05-06 10:45 ` Laxman Dewangan
2016-05-06 14:12 ` Jon Hunter
2016-05-06 14:12 ` Jon Hunter
2016-05-06 10:45 ` [PATCH V4 2/3] soc/tegra: pmc: Correct type of variable for tegra_pmc_readl() Laxman Dewangan
2016-05-06 10:45 ` Laxman Dewangan
[not found] ` <1462531548-12914-3-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-06 14:15 ` Jon Hunter
2016-05-06 14:15 ` Jon Hunter
2016-05-06 10:45 ` [PATCH V4 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage Laxman Dewangan
2016-05-06 10:45 ` Laxman Dewangan
2016-05-06 14:37 ` Jon Hunter
2016-05-06 14:37 ` Jon Hunter
[not found] ` <572CAC20.9030307-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-06 15:32 ` Laxman Dewangan
2016-05-06 15:32 ` Laxman Dewangan
2016-05-08 12:13 ` Jon Hunter [this message]
2016-05-08 12:13 ` Jon Hunter
[not found] ` <572F2D84.3060505-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-11 13:28 ` Laxman Dewangan
2016-05-11 13:28 ` Laxman Dewangan
[not found] ` <57333366.2040500-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-11 15:35 ` Jon Hunter
2016-05-11 15:35 ` Jon Hunter
[not found] ` <5733513E.9080606-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-11 17:22 ` Laxman Dewangan
2016-05-11 17:22 ` Laxman Dewangan
2016-05-11 19:59 ` Jon Hunter
2016-05-11 19:59 ` Jon Hunter
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=572F2D84.3060505@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=gnurou@gmail.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.