lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <573D70E8.3070802@nvidia.com>
Date:	Thu, 19 May 2016 13:23:12 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	<thierry.reding@...il.com>, <airlied@...ux.ie>,
	<swarren@...dotorg.org>, <jonathanh@...dia.com>
CC:	<gnurou@...il.com>, <dri-devel@...ts.freedesktop.org>,
	<linux-kernel@...r.kernel.org>, <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH V5 0/3] soc/tegra: Add support for IO pads power and voltage
 control

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?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ