lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 30 Nov 2017 16:22:21 -0800
From:   Kevin Hilman <khilman@...libre.com>
To:     Neil Armstrong <narmstrong@...libre.com>
Cc:     linux-amlogic@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/4] ARM64: dts: meson-gx: fix VPU init for non-vendor u-boot

Neil Armstrong <narmstrong@...libre.com> 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

Powered by blists - more mailing lists