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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 18 Jun 2012 08:56:29 +0900
From:	Sangbeom Kim <sbkim73@...sung.com>
To:	'Mark Brown' <broonie@...nsource.wolfsonmicro.com>
Cc:	'Liam Girdwood' <lrg@...com>, linux-kernel@...r.kernel.org,
	sameo@...ux.intel.com, sbkim01@...il.com
Subject: RE: [PATCH 5/5] regulator: Support AP watchdog reset operation for
 s5m8767a

On Thu, Jun 18, 2012 at 3:53 AM, Mark Brown wrote:
> > Solution
> > - Basic concept: After ap watchdog reset, GPIO configuration is
> > changed by default value
> > - S5M8767A has function of voltage control with gpio (8 levels with 3
> > gpios)
> > - Set bootable voltage on level 0 -> can work with default gpio
> > configuration
> > - In the probing, Change voltage control level from level 0 to level 1
> > - Execute normal dvfs operation on level 1
> > - After watchdog reset, ap gpio is set by default value
> > - PMIC operation mode is changed by ap reset (level1 -> level0)
> > - AP can execute normal boot
> 
> OK, so basically what you're doing is fixing one of the GPIO selected voltage levels so that when
> the AP comes out of reset it'll drive the PMIC into a suitable level for it to boot?  That makes
> sense 
That's right.
The voltage of S5M8767A can be controlled by GPIO.
So, I try to check the status of gpio.
I will resend above patch with adding detail commit message.

Thanks,
Sangbeom.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ