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  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]
Date:	Mon, 5 Jan 2015 06:38:50 -0800
From:	Tim Harvey <>
To:	Mark Brown <>,
	Fabio Estevam <>,
	Philipp Zabel <>,
	Shawn Guo <>
Cc:	linux-kernel <>,
	Lucas Stach <>,
	Silvio F <>,
	Christian Hemp <>,
	Russell King <>,
	Iain Paton <>,
Subject: Re: [PATCH 4/5] cpufreq: imx6q: add ldo-bypass support

On Fri, Dec 19, 2014 at 8:23 AM, Mark Brown <> wrote:
> On Fri, Dec 19, 2014 at 08:17:41AM -0800, Tim Harvey wrote:
>> frequency setpoint. If however you have an external PMIC that is
>> capable of adjusting the VDD_ARM and VDD_SOC to the IMX6 and an
>> appropriate regulator driver is capable of doing so, you must
>> configure the cpu nodes vddarm and vddsoc regulators to those provided
>> by your PMIC and 'bypass' the internal LDO's by setting their scaling
> You're describing the implementation again, not the system.  Describe
> the system then if you want to describe the solution you've come up with
> for modelling it do so separately.
> Please also try to use paragraphs to break up what you're saying a bit.


I'm not sure I'm understanding what your asking for or how to describe
it differently. Fabio / Shawn / Philipp could you help me out here
with the proper explanation of the IMX6 LDO's so that we can make some
progress on getting LDO bypass implemented?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists