[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7h4kfjpe07.fsf@baylibre.com>
Date: Mon, 03 May 2021 16:57:12 -0700
From: Kevin Hilman <khilman@...libre.com>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
narmstrong@...libre.com, linux-amlogic@...ts.infradead.org
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-pm@...r.kernel.org,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Stefan Agner <stefan@...er.ch>
Subject: Re: [PATCH RFC] soc: amlogic: meson-ee-pwrc: Drop the .shutdown
callback from the driver
Martin Blumenstingl <martin.blumenstingl@...glemail.com> writes:
> Stefan reports that rebooting his ODROID-N2+ (using a G12B SoC) results
> in the board hanging. His kernel config uses:
> CONFIG_MESON_EE_PM_DOMAINS=y
> CONFIG_DRM_MESON=m
>
> He reports that his kernel config results in the DRM driver's .shutdown
> callback to be executed after the power domain driver's .shutdown
> callback. That's problematic because meson_ee_pwrc_shutdown disables the
> clock which are used by the VPU IP. This causes the board to hang.
I didn't dig deeply on this yet because this smells very much like an
issue Art reported[1] and fixed.
What kernel version are you using, and does it contain
commit fa0c16caf3d7 (drm: meson_drv add shutdown function)
Kevin
[1] https://lore.kernel.org/dri-devel/20210302042202.3728113-1-art@khadas.com/
Powered by blists - more mailing lists