From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752530AbdLAAWi (ORCPT ); Thu, 30 Nov 2017 19:22:38 -0500 Received: from mail-pl0-f68.google.com ([209.85.160.68]:45104 "EHLO mail-pl0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752237AbdLAAWe (ORCPT ); Thu, 30 Nov 2017 19:22:34 -0500 X-Google-Smtp-Source: AGs4zMabwvWXip0K7Qj2tScHgvA8wrRp1Vyz4fIgn8lZqfiE3Mikj36MP4W7Y7/xmWCktxFvv9tPww== From: Kevin Hilman To: Neil Armstrong Cc: linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/4] ARM64: dts: meson-gx: fix VPU init for non-vendor u-boot Organization: BayLibre References: <1511187597-18248-1-git-send-email-narmstrong@baylibre.com> Date: Thu, 30 Nov 2017 16:22:21 -0800 In-Reply-To: <1511187597-18248-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 20 Nov 2017 15:19:53 +0100") Message-ID: <7hmv33uwjm.fsf@baylibre.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Neil Armstrong writes: > On the Amlogic Gx SoCs (GXBB, GXL & GXM), the VPU power domain is initialized > by the vendor U-Boot code, but running mainline U-boot has been possible > on these SoCs. But lacking such init made the system lock at kernel boot. > > A PM Power Domain driver has been pushed at [1] to solve the main issue. > > This patchset depends on the the following patchsets : > - [1] soc: amlogic: add support for Meson GX VPU Domains > - [2] reset: meson: add level reset support for GX SoC family > - [3] clk: meson: gxbb: Add VPU and VAPB clocks > > Changes since v1 at [4] : > - Dropped hdmi-supply in hdmi node until 4.16 > - set 5v regulator always-on for now v2 applied to v4.15/fixes, Thanks, Kevin