Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
	Lee Jones <lee.jones@linaro.org>,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	devicetree@vger.kernel.org,
	Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH 3/3] mfd: sec-core: Disable buck voltage reset on watchdog falling edge
Date: Tue, 06 Oct 2015 08:49:16 +0900	[thread overview]
Message-ID: <56130C7C.6000207@samsung.com> (raw)
In-Reply-To: <2375080.1KPJ21Fk4I@amdc1976>

On 05.10.2015 22:35, Bartlomiej Zolnierkiewicz wrote:
> 
> Hi,
> 
> On Friday, October 02, 2015 05:25:51 PM Krzysztof Kozlowski wrote:
>> The WRSTBI bit (disabled by default but enabled by bootloader), when
>> set, is responsible for resetting voltages to default values of
>> certain bucks on falling edge of Warm Reset Input pin from AP.
>>
>> However on some boards (with S2MPS13) the pin is pulled down so any
>> suspend will effectively trigger the reset of bucks supplying the power
>> to the little and big cores. In the same time when resuming, these bucks
>> must provide voltage greater or equal to voltage before suspend to match
>> the frequency chosen by cpufreq. If voltage (default value of voltage
>> after reset) is lower than one set by cpufreq before suspend, then
>> system will hang during resuming.
>>
>> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> 
> I tested this (with some additional Exynos5433 patches) and it works
> like expected (suspend/resume issue is fixed).
> 
> Tested-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> 

Thanks!

> You could also add:
> 
> Reported-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> 
> (since the issue got narrowed down and reported to you by me :).

I didn't put it because I wasn't sure who was the author of our report.
I'll wait a one more day for any comments and add it in v2/resend.

BTW, any comments on the binding itself?
Actually I had hard time choosing the name for binding because unlike
the ACOKB the WRSTBI pin is not grounded but pulled down. However it is
quite similar so I stick to the same convention:
 - samsung,s2mps11-acokb-ground
 - samsung,s2mps11-wrstbi-ground


Best regards,
Krzysztof

      reply	other threads:[~2015-10-05 23:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  8:25 [PATCH 1/3] mfd: sec-core: Dump PMIC revision to find out the HW Krzysztof Kozlowski
2015-10-02  8:25 ` [PATCH 2/3] mfd: dt-bindings: Document pulled down WRSTBI pin on S2MPS1X Krzysztof Kozlowski
2015-10-02  8:25 ` [PATCH 3/3] mfd: sec-core: Disable buck voltage reset on watchdog falling edge Krzysztof Kozlowski
     [not found]   ` <1443774351-28766-3-git-send-email-k.kozlowski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-10-05 13:35     ` Bartlomiej Zolnierkiewicz
2015-10-05 23:49       ` Krzysztof Kozlowski [this message]

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=56130C7C.6000207@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=sbkim73@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox