linux-kernel - Re: [PATCH] arm64: dts: rockchip: update cpu opp table for rk3399 op1

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3119382.DFiP2J6FnE@diego>
Date:   Mon, 24 Apr 2017 11:15:48 +0200
From:   Heiko Stübner <heiko@...ech.de>
To:     Caesar Wang <wxt@...k-chips.com>
Cc:     linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, briannorris@...omium.org,
        dianders@...omium.org
Subject: Re: [PATCH] arm64: dts: rockchip: update cpu opp table for rk3399 op1

Am Montag, 24. April 2017, 16:49:08 CEST schrieb Caesar Wang:
> 在 2017年04月24日 16:26, Heiko Stübner 写道:
> > Hi Caesar,
> > 
> > Am Montag, 24. April 2017, 14:18:50 CEST schrieb Caesar Wang:
> >> Update the cpu opp table for rk3399 op1.
> > 
> > Ideally this should contain something about the "why".
> > Are these new voltage settings safer to operate under?
> 
> The before opp table is for earlier batch of rk3399 SoCs,  that's no
> enough for the current and
> newer batch of rk3399 op1. In order to suit for the rk3399 op1, we need
> to little voltages changed.

just to make sure, this is also safe for all the non-chromebook rk3399 socs 
(like the firefly and tv-boxes, etc), right?


Thanks
Heiko