From: Jon Hunter <jonathanh@nvidia.com>
To: Venkat Reddy Talla <vreddytalla@nvidia.com>,
airlied@linux.ie, dri-devel@lists.freedesktop.org,
pdeschrijver@nvidia.com, vivek.gautam@codeaurora.org,
p.zabel@pengutronix.de, thierry.reding@gmail.com,
mperttunen@nvidia.com, mark.rutland@arm.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: talho@nvidia.com, ldewangan@nvidia.com, avienamo@nvidia.com
Subject: Re: [PATCH 1/3] soc/tegra: pmc: set IO pad power state and voltage via pinctrl fw
Date: Thu, 2 Aug 2018 13:21:20 +0100 [thread overview]
Message-ID: <76f4442e-842b-c08f-386d-a7062ed34a19@nvidia.com> (raw)
In-Reply-To: <1533211143-17517-1-git-send-email-vreddytalla@nvidia.com>
On 02/08/18 12:59, Venkat Reddy Talla 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. These groups are referred
> to as IO pads.The power state and voltage control of IO pins
> can be done at IO pads level.
>
> Tegra SoCs support powering down IO pads when they are
> 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 Tegra124, hence SW need not to configure this.
> But from Tegra210, the automatic detection logic has been
> removed, hence SW need to explicitly set the IO pad
> voltage into IO pad configuration registers.
>
> Add support to configure the power state and voltage level
> of the IO pads from client driver via pincontrol framework.
>
> Signed-off-by: Venkat Reddy Talla <vreddytalla@nvidia.com>
This appears to be a duplicate effort of the following which we have
been reviewing ...
https://marc.info/?l=linux-tegra&m=153295930808915&w=2
Cheers
Jon
--
nvpublic
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-02 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 11:59 [PATCH 1/3] soc/tegra: pmc: set IO pad power state and voltage via pinctrl fw Venkat Reddy Talla
2018-08-02 11:59 ` [PATCH 2/3] dt-bindings: tegra: update PMC DT binding with io pads control Venkat Reddy Talla
2018-08-02 11:59 ` [PATCH 3/3] drm/tegra: sor: change io pad power state using new pmc api Venkat Reddy Talla
2018-08-02 12:21 ` Jon Hunter [this message]
2018-08-02 22:21 ` [PATCH 1/3] soc/tegra: pmc: set IO pad power state and voltage via pinctrl fw kbuild test robot
2018-08-02 22:45 ` kbuild test robot
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=76f4442e-842b-c08f-386d-a7062ed34a19@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=airlied@linux.ie \
--cc=avienamo@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mperttunen@nvidia.com \
--cc=p.zabel@pengutronix.de \
--cc=pdeschrijver@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=talho@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=vivek.gautam@codeaurora.org \
--cc=vreddytalla@nvidia.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