public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
	swarren@nvidia.com, andy.shevchenko@gmail.com,
	alcooperx@gmail.com, linux-gpio@vger.kernel.org,
	Heiko Stuebner <heiko@sntech.de>
Subject: Re: [PATCH fixes v3] pinctrl: Really force states during  suspend/resume
Date: Mon, 19 Feb 2018 19:11:16 +0000	[thread overview]
Message-ID: <86po50dcbv.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <913ED32F-36F8-4F31-9221-263DD5599FB2@gmail.com>

On Mon, 19 Feb 2018 18:03:27 +0000,
Florian Fainelli wrote:
> 
> On February 19, 2018 9:25:26 AM PST, Marc Zyngier <maz@misterjones.org> wrote:
> >Hi all,
> >
> >On 2017-03-01 18:32, Florian Fainelli wrote:
> >> In case a platform only defaults a "default" set of pins, but not a
> >> "sleep" set of pins, and this particular platform suspends and 
> >> resumes
> >> in a way that the pin states are not preserved by the hardware, when 
> >> we
> >> resume, we would call pinctrl_single_resume() -> 
> >> pinctrl_force_default()
> >> -> pinctrl_select_state() and the first thing we do is check that the
> >> pins state is the same as before, and do nothing.
> >>
> >> In order to fix this, decouple the actual state change from
> >> pinctrl_select_state() and move it pinctrl_commit_state(), while 
> >> keeping
> >> the p->state == state check in pinctrl_select_state() not to change 
> >> the
> >> caller assumptions. pinctrl_force_sleep() and pinctrl_force_default()
> >> are updated to bypass the state check by calling 
> >> pinctrl_commit_state().
> >>
> >> Fixes: 6e5e959dde0d ("pinctrl: API changes to support multiple states
> >> per device")
> >> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>

[back to using my ARM address]

Hey Florian,

> Hey Marc,
> 
> >
> >I don't often go back over a year worth of LKML, but since this patch 
> >recently landed in mainline as 981ed1bfbc6c, I though I'd use it as an 
> >anchor to report the following:
> >
> >It turns out that this patch completely breaks resume on my
> >rk3399-based Chromebook. Most things are timing out, the box is
> >unusable. And since this is my everyday tool, I'm mildly
> >grumpy. Please don't break my toys! ;-) Reverting this patch on top
> >of 4.16-rc2 makes me productive again...
> >
> >More seriously, I have no idea what's wrong here. It could be a 
> >SoC-related issue, hence Heiko on Cc. I'm happy to test any idea you 
> >could have.
> 
> Can you indicate which DTS file is used for your Chromebook model?

Sure. That's arch/arm64/boot/dts/rockchip/rk3399-gru-kevin.dts, with a
couple of fixes on top (some clocks and big-little idiosyncrasies).

> Sorry about the breakage.

No worries.

	M.

-- 
Jazz is not dead, it just smell funny.

      parent reply	other threads:[~2018-02-19 19:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 18:32 [PATCH fixes v3] pinctrl: Really force states during suspend/resume Florian Fainelli
2017-03-02  8:54 ` Andy Shevchenko
2017-03-02 22:19   ` Florian Fainelli
2017-03-14 10:16     ` Linus Walleij
2017-03-15  2:18       ` Florian Fainelli
2017-03-16 14:08         ` Linus Walleij
2017-06-21 21:23           ` Florian Fainelli
2017-06-29  9:17             ` Linus Walleij
2017-06-29 19:38               ` Florian Fainelli
2017-06-29 22:25                 ` Linus Walleij
2018-02-19 17:25 ` Marc Zyngier
2018-02-19 18:03   ` Florian Fainelli
2018-02-19 18:57     ` Heiko Stuebner
2018-02-19 19:23       ` Marc Zyngier
2018-02-22 15:30         ` Linus Walleij
2018-02-22 18:11           ` Marc Zyngier
2018-02-19 19:11     ` Marc Zyngier [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=86po50dcbv.wl-marc.zyngier@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=alcooperx@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=heiko@sntech.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.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