Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752352AbdHNH4x (ORCPT ); Mon, 14 Aug 2017 03:56:53 -0400 Received: from smtp.csie.ntu.edu.tw ([140.112.30.61]:57066 "EHLO smtp.csie.ntu.edu.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751819AbdHNH4v (ORCPT ); Mon, 14 Aug 2017 03:56:51 -0400 MIME-Version: 1.0 In-Reply-To: References: <1502560442-17715-1-git-send-email-jteki@openedev.com> From: Chen-Yu Tsai Date: Mon, 14 Aug 2017 15:56:27 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [linux-sunxi] [PATCH v2] arm64: allwinner: a64: Add A64-OLinuXino initial support To: Jagan Teki Cc: Chen-Yu Tsai , Maxime Ripard , Icenowy Zheng , Rob Herring , Mark Rutland , Catalin Marinas , Will Deacon , Michael Trimarchi , linux-arm-kernel , devicetree , linux-kernel , linux-sunxi , Support - OLIMEX Ltd , Jagan Teki Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1968 Lines: 73 On Mon, Aug 14, 2017 at 3:34 PM, Jagan Teki wrote: > On Mon, Aug 14, 2017 at 12:38 PM, Chen-Yu Tsai wrote: >> Hi, >> >> On Sun, Aug 13, 2017 at 1:54 AM, Jagan Teki wrote: >>> From: Jagan Teki >>> >>> OLimex A64-OLinuXino is an open-source hardware board >>> using the Allwinner A64 SOC. >>> >>> OLimex A64-OLinuXino has >>> - A64 Quad-core Cortex-A53 64bit >>> - 1GB or 2GB RAM DDR3L @ 672Mhz >>> - microSD slot and 4/8/16GB eMMC >>> - Debug TTL UART >>> - HDMI >>> - LCD >>> - IR receiver >>> - 5V DC power supply >> >> Have you tried out Ethernet? > > Not, tested yet. Will send separate patch. OK. [...] >>> + >>> +®_aldo2 { >>> + regulator-always-on; >>> + regulator-min-microvolt = <3300000>; >>> + regulator-max-microvolt = <3300000>; >> >> Schematic says 1.8V? > > I saw ALD02 VCC-PL=3.3v on schematic. Ah. I see they changed it in a rev. B. Lets use 3.3V then. >> >>> + regulator-name = "vcc-pl"; >>> +}; >>> + >>> +®_aldo3 { >>> + regulator-always-on; >>> + regulator-min-microvolt = <3000000>; >>> + regulator-max-microvolt = <3000000>; >>> + regulator-name = "vcc-pll-avcc"; >>> +}; >>> + >>> +®_dcdc1 { >>> + regulator-always-on; >>> + regulator-min-microvolt = <3300000>; >>> + regulator-max-microvolt = <3300000>; >>> + regulator-name = "vcc-3v3"; >>> +}; >>> + >>> +®_dcdc2 { >>> + regulator-always-on; >>> + regulator-min-microvolt = <1100000>; >>> + regulator-max-microvolt = <1100000>; >> >> The SoC has a wider range than a fixed voltage for the CPUs. > > So, max 1.1v can't enough CPUs? thought similar behavior with pine64? The recommended operating conditions says 1.04 ~ 1.3 V for CPUx, while the typical voltage is 1.1V. The regulator constraints should match the datasheet, especially for power rails that are involved in DVFS. ChenYu