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
| ||
|
Message-id: <a42670aa-b3df-7a53-8ed2-f3acd97fd0d4@samsung.com> Date: Tue, 12 Dec 2017 11:17:36 +0100 From: Marek Szyprowski <m.szyprowski@...sung.com> To: Krzysztof Kozlowski <krzk@...nel.org>, Javier Martinez Canillas <javierm@...hat.com> Cc: linux-kernel@...r.kernel.org, Guillaume Tucker <guillaume.tucker@...labora.com>, Daniel Vetter <daniel.vetter@...ll.ch>, Shuah Khan <shuahkh@....samsung.com>, devicetree@...r.kernel.org, Kukjin Kim <kgene@...nel.org>, Russell King <linux@...linux.org.uk>, linux-samsung-soc@...r.kernel.org, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH v2] ARM: dts: exynos: Enable Mixer node for Exynos5800 Peach Pi machine Hi Krzysztof, On 2017-12-12 11:09, Krzysztof Kozlowski wrote: > On Tue, Dec 12, 2017 at 10:55 AM, Krzysztof Kozlowski <krzk@...nel.org> wrote: >> On Tue, Dec 12, 2017 at 8:42 AM, Javier Martinez Canillas >> <javierm@...hat.com> wrote: >>> Commit 1cb686c08d12 ("ARM: dts: exynos: Add status property to Exynos 542x >>> Mixer nodes") disabled the Mixer node by default in the DTSI and enabled >>> for each Exynos 542x DTS. But unfortunately it missed to enable it for the >>> Exynos5800 Peach Pi machine, since the 5800 is also an 542x SoC variant. >>> >>> Fixes: 1cb686c08d12 ("ARM: dts: exynos: Add status property to Exynos 542x Mixer nodes") >>> Signed-off-by: Javier Martinez Canillas <javierm@...hat.com> >>> Acked-by: Marek Szyprowski <m.szyprowski@...sung.com> >>> >>> --- >>> >>> Changes in v2: >>> - Remove RFT tag. >> Thanks guys! However I still would like to see a tested-by for this on >> Peach Pi (AFAIU, Marek's only acked the code/solution). > On the other hand I could just apply it for my for-next branch and > we'll see if it fixes kernel-ci boot tests... Not a nice way of > testing but apparently no one has Peach Pi. Frankly, I don't expect that this will solve the boot hang issue on PeachPi. However it should at least hide the unbalanced regulator issue. Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland
Powered by blists - more mailing lists