linux-kernel - Re: [PATCH v2] ARM: dts: imx6ull: add Toradex Colibri iMX6ULL support

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] [day] [month] [year] [list]

Message-ID: <20180209025817.GJ31910@dragon>
Date:   Fri, 9 Feb 2018 10:58:18 +0800
From:   Shawn Guo <shawnguo@...nel.org>
To:     stefan@...er.ch
Cc:     kernel@...gutronix.de, fabio.estevam@....com, robh+dt@...nel.org,
        mark.rutland@....com, linux-arm-kernel@...ts.infradead.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        max.oss.09@...il.com, marcel.ziswiler@...adex.com
Subject: Re: [PATCH v2] ARM: dts: imx6ull: add Toradex Colibri iMX6ULL support

On Thu, Feb 08, 2018 at 10:25:47AM +0100, stefan@...er.ch wrote:
> On 08.02.2018 08:47, Shawn Guo wrote:
> > On Tue, Feb 06, 2018 at 05:49:03PM +0100, Stefan Agner wrote:
> >> Add support for the Computer on Module Colibri iMX6ULL and its
> >> Bluetooth/Wifi variant along with the development/evaluation carrier
> >> board device trees. Follow the usual hierarchic include model,
> >> maintaining shared configuration in imx6ull-colibri.dtsi and
> >> imx6ull-colibri-eval-v3.dtsi respectively.
> >>
> >> Signed-off-by: Stefan Agner <stefan@...er.ch>
> >> ---
> >> This depends on the following patchsets work:
> >> - https://lkml.org/lkml/2018/1/6/129 (applied)
> >> - https://lkml.org/lkml/2018/1/10/998 (applied)
> >> - https://www.spinics.net/lists/arm-kernel/msg632671.html (pending, required)
> >> - https://lkml.org/lkml/2018/1/18/850 (only for highest CPU frequency)
> > 
> > So the only dependency is the cpufreq change now.  So we have two
> > options:
> > 
> > 1. Hold the patch until the cpufreq change appear on my tree.  That
> >    will require us wait for another release cycle.
> > 
> > 2. Drop the highest CPU frequency, so that we can apply the patch right
> >    away, and add that setpoint after dependant cpufreq change lands
> >    mainline.
> 
> The way cpufreq currently works is that for everything higher than
> 396MHz it just will set the CPU parent to pll2_bus_clk which can go up
> to 528MHz. Also voltage should be within operation range even for
> 528MHz.
> 
> So I think we can safely merge the current device tree.

Okay, thanks for the info.  Patch applied.

Shawn