From: Laxman Dewangan <ldewangan@nvidia.com>
To: thierry.reding@gmail.com, airlied@linux.ie,
swarren@wwwdotorg.org, jonathanh@nvidia.com
Cc: gnurou@gmail.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH V5 0/3] soc/tegra: Add support for IO pads power and voltage control
Date: Thu, 19 May 2016 13:23:12 +0530 [thread overview]
Message-ID: <573D70E8.3070802@nvidia.com> (raw)
In-Reply-To: <1463055706-17744-1-git-send-email-ldewangan@nvidia.com>
Hi Jon/Thierry,
On Thursday 12 May 2016 05:51 PM, 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.
>
> Tegra124 onwards IO pads support the power down state when system is
> active. The voltage levels on IO pads are auto detected on Tegra124/
> Tegra132 but it is not in Tegra210. For Tegra210, the SW need to
> explicitly configure the voltage levels of IO pads
>
> This series add the interface for the IO pad power state and voltage
> configurations. Modifies the client to use new APIs.
> Register the child devices to provide the client interface to configure
> IO pads power state and voltage from Device tree.
>
Any comment on this series?
prev parent reply other threads:[~2016-05-19 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 12:21 [PATCH V5 0/3] soc/tegra: Add support for IO pads power and voltage control Laxman Dewangan
2016-05-12 12:21 ` [PATCH V5 1/3] soc/tegra: pmc: Use BIT macro for register field definition Laxman Dewangan
[not found] ` <1463055706-17744-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-12 12:21 ` [PATCH V5 2/3] soc/tegra: pmc: Correct type of variable for tegra_pmc_readl() Laxman Dewangan
2016-05-12 12:21 ` [PATCH V5 3/3] soc/tegra: pmc: Add support for IO pads power state and voltage Laxman Dewangan
2016-05-19 15:54 ` Jon Hunter
[not found] ` <573DE19C.8090704-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-19 16:13 ` Laxman Dewangan
[not found] ` <573DE61D.6080203-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-20 8:58 ` Jon Hunter
2016-05-20 9:34 ` Jon Hunter
2016-05-20 10:02 ` Jon Hunter
[not found] ` <573EE0CB.7000807-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-20 9:59 ` Laxman Dewangan
[not found] ` <573EE015.6050600-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-05-20 10:28 ` Jon Hunter
2016-05-19 7:53 ` Laxman Dewangan [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=573D70E8.3070802@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@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 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).