At 1.1V & maximum cpufreq my Orange Pi PC2 boards kernel panic 90% of the time. This patch works perfectly for my board. Please apply patch to mainline.
Hopefully the idea is to run the regulator at it's default speed (& set a low maximum CPU speed from u-boot) then once the kernel has taken over control, set the regulator to (some-higher-voltage)V and set the cpufreq to it's maximum. This would keep the boot-loader code fairly minimal. Cheers! On Monday, November 6, 2017 at 8:10:46 AM UTC, Jagan Teki wrote: > > On Fri, Nov 3, 2017 at 10:00 PM, Maxime Ripard > <[email protected] <javascript:>> wrote: > > On Fri, Nov 03, 2017 at 02:21:51PM +0530, Jagan Teki wrote: > >> On Thu, Nov 2, 2017 at 7:26 PM, Maxime Ripard > >> <[email protected] <javascript:>> wrote: > >> > On Wed, Nov 01, 2017 at 08:31:46AM +0800, Icenowy Zheng wrote: > >> >> 在 2017-10-31 21:54，Maxime Ripard 写道： > >> >> > On Tue, Oct 31, 2017 at 04:05:36PM +0800, [email protected] > <javascript:> wrote: > >> >> > > 在 2017-10-31 15:57，Jagan Teki 写道： > >> >> > > > On Tue, Oct 31, 2017 at 5:06 AM, Icenowy Zheng <[email protected] > <javascript:>> wrote: > >> >> > > > > Some H5 boards are designed to start at 1.1V CPUx voltage > (e.g. Nano > >> >> > > > > Pi > >> >> > > > > NEO2), which may not work properly at 1008MHz if the chip's > quality is > >> >> > > > > not so good. > >> >> > > > > > >> >> > > > > Lower the default CPUx frequency of H5 to 816MHz. > >> >> > > > > > >> >> > > > > Signed-off-by: Icenowy Zheng <[email protected] <javascript:>> > >> >> > > > > --- > >> >> > > > > arch/arm/mach-sunxi/Kconfig | 2 +- > >> >> > > > > 1 file changed, 1 insertion(+), 1 deletion(-) > >> >> > > > > > >> >> > > > > diff --git a/arch/arm/mach-sunxi/Kconfig > b/arch/arm/mach-sunxi/Kconfig > >> >> > > > > index 09cfec6f57..1fededd0a3 100644 > >> >> > > > > --- a/arch/arm/mach-sunxi/Kconfig > >> >> > > > > +++ b/arch/arm/mach-sunxi/Kconfig > >> >> > > > > @@ -397,9 +397,9 @@ config SYS_CLK_FREQ > >> >> > > > > default 1008000000 if MACH_SUN5I > >> >> > > > > default 1008000000 if MACH_SUN6I > >> >> > > > > default 912000000 if MACH_SUN7I > >> >> > > > > + default 816000000 if MACH_SUN50I || MACH_SUN50I_H5 > >> >> > > > > default 1008000000 if MACH_SUN8I > >> >> > > > > >> >> > > > Even orangepi pc2 has 1.1v after power-on and it's work fine > [1] did > >> >> > > > you find an issue with neo2? > >> >> > > >> >> > So you have one single model that fails, and you change the > default > >> >> > frequency of all the boards using that SoC? > >> >> > >> >> But I think we have already set the default frequency to 816MHz for > >> >> A64, and it seems that several H5 boards are designed to start at > 1.1v > >> >> (see the notes by Jagan above). > >> >> > >> >> > > >> >> > It seems a bit overkill. > >> >> > > >> >> > I guess we have two solutions: > >> >> > 1) Change the frequency in that board config > >> >> > 2) Change the voltage in that board config > >> >> > >> >> NEO2 don't have any voltage adjusting, it's fixed at 1.1V. > >> >> > >> >> And according to the Orange Pi PC2 and Prime schematics, they both > >> >> start at 1.1V. (The Prime schematics even says "For H5 adjust > >> >> VDD-CPUX to 1.1V). > >> > > >> > And what about the Zero Plus 2 ? > >> > >> Same equation with same reg values, but missing reg names on specific > >> register area Page 7 [4] but hope both were same. > > > > Ok, so it's not some H5 boards, it's all of them. It makes sense then, > > once the commit log has been changed. > > Let me test and will apply all fine. > > thanks! > -- > Jagan Teki > Free Software Engineer | www.openedev.com > U-Boot, Linux | Upstream Maintainer > Hyderabad, India. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
