On Tuesday 08 November 2016 09:16 PM, Linus Walleij wrote:
On Tue, Nov 8, 2016 at 2:35 PM, Laxman Dewangan wrote:
There is two types of configuration in given platform, the IO voltage does
not get change (fixed in given platform) and in some of cases, get change
dynamically like SDIO3.0 where
On Tuesday 08 November 2016 08:12 PM, Thierry Reding wrote:
* PGP Signed by an unknown key
On Tue, Nov 08, 2016 at 07:05:26PM +0530, Laxman Dewangan wrote:
Yes, it can be integrated with the regulator handle and then it can call the
required configurations through notifier and regulator_get_v
On Tue, Nov 8, 2016 at 2:35 PM, Laxman Dewangan wrote:
> There is two types of configuration in given platform, the IO voltage does
> not get change (fixed in given platform) and in some of cases, get change
> dynamically like SDIO3.0 where the voltage switches to 3.3V and 1.8V.
>
> Yes, it can b
On Tue, Nov 08, 2016 at 07:05:26PM +0530, Laxman Dewangan wrote:
>
> On Tuesday 08 November 2016 06:59 PM, Linus Walleij wrote:
> > On Tue, Nov 8, 2016 at 11:20 AM, Laxman Dewangan
> > wrote:
> > > On Tuesday 08 November 2016 03:45 PM, Linus Walleij wrote:
> > > > If you can *actually* change th
On Tuesday 08 November 2016 06:59 PM, Linus Walleij wrote:
On Tue, Nov 8, 2016 at 11:20 AM, Laxman Dewangan wrote:
On Tuesday 08 November 2016 03:45 PM, Linus Walleij wrote:
If you can *actually* change the volatage, it needs to be modeled
as a (fixed voltage?) regulator, not as a custom prop
On Tue, Nov 8, 2016 at 11:20 AM, Laxman Dewangan wrote:
> On Tuesday 08 November 2016 03:45 PM, Linus Walleij wrote:
>> If you can *actually* change the volatage, it needs to be modeled
>> as a (fixed voltage?) regulator, not as a custom property for the pin
>> control attributes. I guess you def
On Tuesday 08 November 2016 03:45 PM, Linus Walleij wrote:
On Mon, Nov 7, 2016 at 6:41 AM, Laxman Dewangan wrote:
On Saturday 05 November 2016 03:54 AM, Linus Walleij wrote:
On Wed, Nov 2, 2016 at 10:09 AM, Laxman Dewangan
()
On Tegra124, the IO power rail source is auto detected by So
On Mon, Nov 7, 2016 at 6:41 AM, Laxman Dewangan wrote:
> On Saturday 05 November 2016 03:54 AM, Linus Walleij wrote:
>> On Wed, Nov 2, 2016 at 10:09 AM, Laxman Dewangan
()
>>> On Tegra124, the IO power rail source is auto detected by SoC and hence
>>> it is only require to configure in low po
On Saturday 05 November 2016 03:54 AM, Linus Walleij wrote:
On Wed, Nov 2, 2016 at 10:09 AM, Laxman Dewangan wrote:
NVIDIA Tegra124 and later SoCs support the multi-voltage level and
low power state of some of its IO pads. The IO pads can work in
the voltage of the 1.8V and 3.3V of IO power r
On Wed, Nov 2, 2016 at 10:09 AM, Laxman Dewangan wrote:
> NVIDIA Tegra124 and later SoCs support the multi-voltage level and
> low power state of some of its IO pads. The IO pads can work in
> the voltage of the 1.8V and 3.3V of IO power rail sources. When IO
> interface are not used then IO pads
Hi Laxman,
[auto build test ERROR on tegra/for-next]
[also build test ERROR on v4.9-rc3 next-20161028]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Laxman-Dewangan/pinctrl-tegra-Add-support-fo
NVIDIA Tegra124 and later SoCs support the multi-voltage level and
low power state of some of its IO pads. The IO pads can work in
the voltage of the 1.8V and 3.3V of IO power rail sources. When IO
interface are not used then IO pads can be configure in low power
state to reduce the power from that
12 matches
Mail list logo
