[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <459cb125-a3e2-8f1e-b960-011020d41b3c@gmx.de>
Date: Wed, 20 Jun 2018 07:59:34 +0200
From: Heinrich Schuchardt <xypron.glpk@....de>
To: Heiko Stuebner <heiko@...ech.de>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Shawn Lin <shawn.lin@...k-chips.com>,
Vagrant Cascadian <vagrant@...ian.org>,
Enric Balletbo i Serra <enric.balletbo@...labora.com>,
Pierre-Hugues Husson <phh@....me>,
Jianqun Xu <jay.xu@...k-chips.com>,
Kever Yang <kever.yang@...k-chips.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] arm64: dts: rockchip: correct voltage selector
Firefly-RK3399
On 06/20/2018 01:21 AM, Heiko Stuebner wrote:
> Hi Heinrich,
>
> Am Donnerstag, 14. Juni 2018, 14:55:27 CEST schrieb Heiko Stuebner:
>> Am Montag, 4. Juni 2018, 19:15:23 CEST schrieb Heinrich Schuchardt:
>>> Without this patch the Firefly-RK3399 board boot process hangs after these
>>> lines:
>>>
>>> fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!
>>> fan53555-reg: supplied by vcc_sys
>>> vcc1v8_s3: supplied by vcc_1v8
>>>
>>> Blacklisting driver fan53555 allows booting.
>>>
>>> The device tree uses a value of fcs,suspend-voltage-selector different to
>>> any other board.
>>>
>>> Changing this setting to the usual value is sufficient to enable booting.
>>>
>>> Signed-off-by: Heinrich Schuchardt <xypron.glpk@....de>
>>
>> applied for 4.19.
>
> and dropped again.
>
> Sadly it looks like the patch causes conflicts with at least one firefly
> board in a kernelci lab. My own is currently not ready to use, so I cannot
> look myself right now.
>
> The issue kernelci people described sounded quite a lot like the one
> in your commit message, so my current theory is that the
> suspend-voltage-selector must in some form corespond to the
> cpu_b_sleep_h gpio setting we're currently not handling at all, which
> would therefore depend on how the bootloader sets this up.
>
Hi Heiko,
please, provide a link to the log displaying the issue and the contact
who can provide the exact setup.
I have been testing with U-Boot as boot loader.
Best regards
Heinrich
Powered by blists - more mailing lists