From: Jon Hunter <jonathanh@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
thierry.reding@gmail.com, airlied@linux.ie,
swarren@wwwdotorg.org
Cc: gnurou@gmail.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH V7 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage
Date: Tue, 24 May 2016 11:48:51 +0100 [thread overview]
Message-ID: <57443193.5010900@nvidia.com> (raw)
In-Reply-To: <5742C773.6080609@nvidia.com>
On 23/05/16 10:03, Jon Hunter wrote:
>
> On 20/05/16 15:45, Laxman Dewangan wrote:
>> The IO pins of Tegra SoCs are grouped for common control of IO
>> interface like setting voltage signal levels and power state of
>> the interface. The group is generally referred as IO pads. The
>> power state and voltage control of IO pins can be done at IO pads
>> level.
>>
>> Tegra generation SoC supports the power down of IO pads when it
>> is not used even in the active state of system. This saves power
>> from that IO interface. Also it supports multiple voltage level
>> in IO pins for interfacing on some of pads. The IO pad voltage is
>> automatically detected till T124, hence SW need not to configure
>> this. But from T210, the automatically detection logic has been
>> removed, hence SW need to explicitly set the IO pad voltage into
>> IO pad configuration registers.
>>
>> Add support to set the power states and voltage level of the IO pads
>> from client driver. The implementation for the APIs are in generic
>> which is applicable for all generation os Tegra SoC.
>>
>> IO pads ID and information of bit field for power state and voltage
>> level controls are added for Tegra124, Tegra132 and Tegra210. The SOR
>> driver is modified to use the new APIs.
>>
>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>
> Thanks. I will defer to Thierry on how this should be organised for
> merging but I am happy with the code. There is one minor typo below, but
> otherwise ...
>
> Acked-by: Jon Hunter <jonathanh@nvidia.com>
I have tested this on a Tegra124 Nyan Big and verified that the SOR IO
pads are turning on and off and no errors are seen. I have also boot
tested this series on our upstream test farm and not seen any
regressions. So ...
Tested-by: Jon Hunter <jonathanh@nvidia.com>
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>
Cc: <gnurou@gmail.com>, <dri-devel@lists.freedesktop.org>,
<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V7 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage
Date: Tue, 24 May 2016 11:48:51 +0100 [thread overview]
Message-ID: <57443193.5010900@nvidia.com> (raw)
In-Reply-To: <5742C773.6080609@nvidia.com>
On 23/05/16 10:03, Jon Hunter wrote:
>
> On 20/05/16 15:45, Laxman Dewangan wrote:
>> The IO pins of Tegra SoCs are grouped for common control of IO
>> interface like setting voltage signal levels and power state of
>> the interface. The group is generally referred as IO pads. The
>> power state and voltage control of IO pins can be done at IO pads
>> level.
>>
>> Tegra generation SoC supports the power down of IO pads when it
>> is not used even in the active state of system. This saves power
>> from that IO interface. Also it supports multiple voltage level
>> in IO pins for interfacing on some of pads. The IO pad voltage is
>> automatically detected till T124, hence SW need not to configure
>> this. But from T210, the automatically detection logic has been
>> removed, hence SW need to explicitly set the IO pad voltage into
>> IO pad configuration registers.
>>
>> Add support to set the power states and voltage level of the IO pads
>> from client driver. The implementation for the APIs are in generic
>> which is applicable for all generation os Tegra SoC.
>>
>> IO pads ID and information of bit field for power state and voltage
>> level controls are added for Tegra124, Tegra132 and Tegra210. The SOR
>> driver is modified to use the new APIs.
>>
>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
>
> Thanks. I will defer to Thierry on how this should be organised for
> merging but I am happy with the code. There is one minor typo below, but
> otherwise ...
>
> Acked-by: Jon Hunter <jonathanh@nvidia.com>
I have tested this on a Tegra124 Nyan Big and verified that the SOR IO
pads are turning on and off and no errors are seen. I have also boot
tested this series on our upstream test farm and not seen any
regressions. So ...
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Cheers
Jon
next prev parent reply other threads:[~2016-05-24 10:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 14:45 [PATCH V7 0/3] soc/tegra: Add support for IO pads power and voltage control Laxman Dewangan
2016-05-20 14:45 ` Laxman Dewangan
2016-05-20 14:45 ` [PATCH V7 1/3] soc/tegra: pmc: Use BIT macro for register field definition Laxman Dewangan
2016-05-20 14:45 ` Laxman Dewangan
2016-05-20 14:45 ` [PATCH V7 2/3] soc/tegra: pmc: Correct type of variable for tegra_pmc_readl() Laxman Dewangan
2016-05-20 14:45 ` Laxman Dewangan
2016-05-20 14:45 ` [PATCH V7 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage Laxman Dewangan
2016-05-20 14:45 ` Laxman Dewangan
[not found] ` <1463755530-20941-4-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-23 9:03 ` Jon Hunter
2016-05-23 9:03 ` Jon Hunter
2016-05-24 10:48 ` Jon Hunter [this message]
2016-05-24 10:48 ` Jon Hunter
[not found] ` <57443193.5010900-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-06-16 13:16 ` Laxman Dewangan
2016-06-16 13:16 ` Laxman Dewangan
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=57443193.5010900@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.