Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp5711082ybl; Tue, 10 Dec 2019 10:14:07 -0800 (PST) X-Google-Smtp-Source: APXvYqyDb2DvO0zGoxFYIz36gXE8JfL1B1RrlsuFY2YmZ4jTlH5vwchZO69fnSNIVV4U98sVMavY X-Received: by 2002:aca:534f:: with SMTP id h76mr124305oib.23.1576001647153; Tue, 10 Dec 2019 10:14:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576001647; cv=none; d=google.com; s=arc-20160816; b=GEczUWv8JX9A803G2DRmqP6AEeKKDvJykE38Nu0UUB8V3P8FMJBPlwhXBx9XWq2wbX l5Abew2pqHOhYdcLJs0VJX/4ZHKzXDoIwiQmPWZGOr/UpnAZEQpJfuqlWDZyd/LriHeK SM8F3cQCQSABDBKP8s7HGcfEsFDEk0/J5VrFWFOfG4y4hBwPBmKasJroKW5ab9qeZMpo rC1Y5V0alfyj8y2BrXU2YJlvqvF7Wtf6NJiJw+n7epRhgdUssxsZElVxxJru0gf48TT+ PCsNoM5XLyA7NAXOpdf5PbTK08cyVlfE+Z1jGgbnm71UUuahITU3bpn/fysZfjJcRzo6 3mWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=4lLGRmsliIpZ0UpKU0IEWW602jVUv7+6lHITbij3O5Y=; b=mTP+HQz5T1Nwuc7WdjF33vlxBR1IqXCpM02MyElXFgx39A1Jac2zQRCUVQBGFrrS3j uNYYD6lKbGg6N1BPjO3blgNLGWjBJFq2IdvFgMtDCzawMMbRKrUWUpCHopIQ6iKoUThL PI3/EenC3mBVc5RrMshfnFRMy0CCgO55CeDwtVcts4BIzLzhBmaTxRgqE831cc44bEPi vMy+aLQ03HD24eSa9JKtgqL5WxcfZkFTjBmnL6Dw+qaSJYWbwflI3LDDJL2WxlmslUCy 5Ks5OaI9qwS8aLTAQC0SyCOE2tFdWNgCRjuacIUrnBLcb/w9XtxyC348nX3hLJ9yDlwH 0cmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=Ax41RgSa; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r14si2146445oic.12.2019.12.10.10.13.53; Tue, 10 Dec 2019 10:14:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@baylibre-com.20150623.gappssmtp.com header.s=20150623 header.b=Ax41RgSa; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727749AbfLJSNU (ORCPT + 99 others); Tue, 10 Dec 2019 13:13:20 -0500 Received: from mail-pj1-f65.google.com ([209.85.216.65]:45968 "EHLO mail-pj1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727349AbfLJSNU (ORCPT ); Tue, 10 Dec 2019 13:13:20 -0500 Received: by mail-pj1-f65.google.com with SMTP id r11so7697672pjp.12 for ; Tue, 10 Dec 2019 10:13:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=4lLGRmsliIpZ0UpKU0IEWW602jVUv7+6lHITbij3O5Y=; b=Ax41RgSauchkK4JBfY5KiQhx0ZqAGsHlTIabiht9+ufmYPy0A/k6fzpIOehD7/e1BZ rVNN9fQqcCTUysbKXiB+vDRvErr1DyzQPtKiTYcJqj2GHjmATSk3qucVeOLVRCkOhEIu K5dAVffJQTTNp4WTUL3ki2V3LvaaviZN1KCbOON0El12ZWTLGoM+UwftSpRs5Plgaxb3 JVbzGapJbO730NFVsQnawfZ+KVkgcjfTaxggwi194/nxW0zjNi9K7TZVjJ07vcCzE4r5 L/qmEmEiYuVsMLunBZzzlhPYONXzzXDmajP/VEpXPY6582YOziMrl931APa+/HAqnF5W wXGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=4lLGRmsliIpZ0UpKU0IEWW602jVUv7+6lHITbij3O5Y=; b=dNBH5Uijm4WPGjQEhta3aMKUPUHRFVqkOtVqZnsFyhxeW8ElZRrmK8N1OXT82xqGnH YOmn71fiWn7uflFYiA47HYHb+whO6PY8IxJ82GetmkBAU4H9EokasnKr/6KMvHaRXpEH U70qvpXVNUT8NtczAXUfy6gmJuGddOtXCUOgiJF4nzKa3ltIU8z6lZYl5njB6vTSRM3X g4P7U72rHBNJbGSsM3ayf+KlzgQRRj6+GGHxBCW/1AtSV4W6PmxUUZHWCI+iWI0D4QEU GQvBMhsuBvuSimMZ+Ue2G8H/X5FLEzaaVZUkw0G1uTwydHr6jtKHAXM6XPPhlHA3hQTj plBg== X-Gm-Message-State: APjAAAWhGf9tFTNkGU6LNHJDzDc4/icGsewBZMUBjTpyTT1kUKe4tmaY iW/uW9VC26VYOVHPFd0n5SGvRA== X-Received: by 2002:a17:902:b611:: with SMTP id b17mr22648668pls.210.1576001599750; Tue, 10 Dec 2019 10:13:19 -0800 (PST) Received: from localhost (c-71-197-186-152.hsd1.wa.comcast.net. [71.197.186.152]) by smtp.gmail.com with ESMTPSA id u123sm1382107pfb.109.2019.12.10.10.13.18 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 10 Dec 2019 10:13:18 -0800 (PST) From: Kevin Hilman To: Anand Moon , Neil Armstrong Cc: Rob Herring , Martin Blumenstingl , Jerome Brunet , devicetree , linux-arm-kernel , linux-amlogic@lists.infradead.org, Linux Kernel Subject: Re: [RFC-next 0/1] Odroid C2: Enable DVFS for cpu In-Reply-To: References: <20191101143126.2549-1-linux.amoon@gmail.com> <7hfthtrvvv.fsf@baylibre.com> Date: Tue, 10 Dec 2019 10:13:18 -0800 Message-ID: <7hfthsqcap.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Anand Moon writes: > Hi Neil / Kevin, > > On Tue, 10 Dec 2019 at 14:13, Neil Armstrong wrote: >> >> On 09/12/2019 23:12, Kevin Hilman wrote: >> > Anand Moon writes: >> > >> >> Some how this patch got lost, so resend this again. >> >> >> >> [0] https://patchwork.kernel.org/patch/11136545/ >> >> >> >> This patch enable DVFS on GXBB Odroid C2. >> >> >> >> DVFS has been tested by running the arm64 cpuburn >> >> [1] https://github.com/ssvb/cpuburn-arm/blob/master/cpuburn-a53.S >> >> PM-QA testing >> >> [2] https://git.linaro.org/power/pm-qa.git [cpufreq testcase] >> >> >> >> Tested on latest U-Boot 2019.07-1 (Aug 01 2019 - 23:58:01 +0000) Arch Linux ARM >> > >> > Have you tested with the Harkernel u-boot? >> > >> > Last I remember, enabling CPUfreq will cause system hangs with the >> > Hardkernel u-boot because of improperly enabled frequencies, so I'm not >> > terribly inclined to merge this patch. > > HK u-boot have many issue with loading the kernel, with load address > *it's really hard to build the kernel for HK u-boot*, > to get the configuration correctly. > > Well I have tested with mainline u-boot with latest ATF . > I would prefer mainline u-boot for all the Amlogic SBC, since > they sync with latest driver changes. Yes, we would all prefer mainline u-boot, but the mainline kernel needs to support the vendor u-boot that is shipping with the boards. So until Hardkernel (and other vendors) switch to mainline u-boot we do not want to have upstream kernel defaults that will not boot with the vendor u-boot. We can always support these features, but they just cannot be enabled by default. Kevin