All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sangbeom Kim <sbkim73@samsung.com>
To: "'Mark Brown'" <broonie@opensource.wolfsonmicro.com>
Cc: "'Liam Girdwood'" <lrg@ti.com>,
	linux-kernel@vger.kernel.org, sameo@linux.intel.com,
	sbkim01@gmail.com
Subject: RE: [PATCH 5/5] regulator: Support AP watchdog reset operation for s5m8767a
Date: Thu, 14 Jun 2012 09:01:39 +0900	[thread overview]
Message-ID: <04ad01cd49c0$df565d20$9e031760$@com> (raw)
In-Reply-To: <20120613174620.GD7804@opensource.wolfsonmicro.com>

Hi Mark,
I'm sorry for insufficient explanation.
Basically, PMIC can't know status of ap reset.
Problem can be happened like below.

- AP Bootable lowest arm voltage: 0.9v
- AP arm voltage table for DVFS: 0.8v, 0.9v, 1.0v
- During AP works on 0.8v, watchdog reset is asserted
- AP can't boot, because vdd arm is still 0.8v

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

If you have any question, email me again.
Thanks,
Sangbeom.

> -----Original Message-----
> From: Mark Brown [mailto:broonie@opensource.wolfsonmicro.com]
> Sent: Thursday, June 14, 2012 2:46 AM
> To: Sangbeom Kim
> Cc: 'Liam Girdwood'; linux-kernel@vger.kernel.org; sameo@linux.intel.com; sbkim01@gmail.com
> Subject: Re: [PATCH 5/5] regulator: Support AP watchdog reset operation for s5m8767a
> 
> On Wed, Jun 13, 2012 at 05:28:47PM +0900, Sangbeom Kim wrote:
> > After AP watchdog reset, S5M8767A should be reset too.
> > If AP is set on lowest voltage, AP can't execute boot sequence.
> > This patch support watchdog reset of s5m8767.
> 
> It's really hard to see how this patch addresses the issue above - could you explain in more
> detail, please?


  reply	other threads:[~2012-06-14  0:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13  8:28 [PATCH 5/5] regulator: Support AP watchdog reset operation for s5m8767a Sangbeom Kim
2012-06-13 17:46 ` Mark Brown
2012-06-14  0:01   ` Sangbeom Kim [this message]
2012-06-17 18:53     ` Mark Brown
2012-06-17 23:56       ` Sangbeom Kim

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='04ad01cd49c0$df565d20$9e031760$@com' \
    --to=sbkim73@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=sbkim01@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.