Received: by 10.223.185.116 with SMTP id b49csp3899104wrg; Mon, 26 Feb 2018 07:54:58 -0800 (PST) X-Google-Smtp-Source: AH8x2259foODAp45THoEHOJhmUAsyTO/y01tpzsahlt+VmtAMMUIfpvi2UaZKIvFtLAundwuuoF/ X-Received: by 10.99.95.142 with SMTP id t136mr8587916pgb.94.1519660498489; Mon, 26 Feb 2018 07:54:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519660498; cv=none; d=google.com; s=arc-20160816; b=eqrmK9aMH2Ku0gZJob5DHO6lbEXK26CYWD2PsatNg/NML9CxkI6uDPMLf3nSneAzOY TS9gJRUJDE8RjOQ3uW2THZXcEa2vSHV1PvA7X27qpdgoD9m4XpgsVTw3/Z02+Fv6ztln dD43+wXq1wfTBEHpP3p7oOgzK0MWcl+E28ZwLRfspnfhKFpah42xnuDbODbUkooCRDmo Tz2S68QVkuwLj7si0vInZqmlLFjNREF39cfDNBwHgCA8ZOfKWJguprXgegxU3/u8zpNB rKEb1nWggqcllLEL0VDEnW/tJWEhsdd1W9edGUQD5tEurqXTocgRu6wFFXVGLnLx5JVs xO+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :dkim-signature:arc-authentication-results; bh=Gzv6X1n7sBEKuClE1KLg/QFPit3mDHCl3TagEGKy5ys=; b=MMp/2hPwDXsx82iLWvunXRJEB0F6ZN+p6XtVz4qM/+jZhUqG1vQUsIbm1OFZA1qYlY 7F7cgV4RVVmpsi5o2OHfAjBSUHmIG/npSxygTVVXvaDyx4ei8zEZ4SNeata/2GFevCAX G57jDb/CyHfZbGog6ie6609tMEed9vkKE9QxcP63bgrOCWjaFZUEuGfOyCnmqbJW8yH+ BW9LQC2aCFvAg410kFF1fF1LQCy6EVScYYBs9x22bvF5IcTgoxmDod4GEdbU1B1R5dIy F83DEoEn6PGrMGq2OUIbaRmFYSEH5JzUkcldZlzGiCy7B+1ewXGQch1gvqQDadNC03es As8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sholland.org header.s=fm2 header.b=LqsGQSqM; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=YebqYsfB; 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 t14si6906907pfa.162.2018.02.26.07.54.44; Mon, 26 Feb 2018 07:54:58 -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=@sholland.org header.s=fm2 header.b=LqsGQSqM; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=YebqYsfB; 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 S1752507AbeBZPyJ (ORCPT + 99 others); Mon, 26 Feb 2018 10:54:09 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:42033 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752168AbeBZPyG (ORCPT ); Mon, 26 Feb 2018 10:54:06 -0500 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 46E9D20BCD; Mon, 26 Feb 2018 10:54:05 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Mon, 26 Feb 2018 10:54:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sholland.org; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Gzv6X1n7sBEKuClE1KLg/QFPit3mD HCl3TagEGKy5ys=; b=LqsGQSqMzjfDnAYELd75Z0KTZcYZ2lfIELhtnYJZrkl8z 9gAB7aV7Esy+YrDLy296LitFf/GI1/3wY5hlcvwaEI6h7t/uVKJqf5G68cmVp3l0 FjVZ/kiO04SkfN0298SCLsVtpwJh+tC2pYVjAEhDAyA3ar9RWbpmXk+uoitxbT0i IASFF3wFUmuGiiLzROUR5ydPJKn8ijdUyij/Pmnbb9kKh/8db6JyXeyEJmjl4+7S nT4LApo8lpMV8GgQtOjaRejA4HEe60UZe+PXwCTFjY3Z8sEMUgHTkNO2nScHLAQi tITzPYs8jPoa5VVFlFykFoNJZuf9gZ3u9Me/Xkf5A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Gzv6X1 n7sBEKuClE1KLg/QFPit3mDHCl3TagEGKy5ys=; b=YebqYsfB4PkNjiEsBDpSMM 9Bfqpye8TbDNRZjAFLhsraioaWB9HXwZ3qmnVp4/wEHZdhFbRjSLLVaZCA5WHYlk s8555YXmtn9FzuoupXT5cnmm8754NwVst643JFSdJjuTgxuMnFf+3svZ1mByZrOi d+OfrL30ANNivY5isQEG3HST49H+tVnPaGAocRT9hfe7WLwNaqh/rlVOPamGtpvh 5XJKB8/8E3W468pm9dAoya1cs4TzFUzHZkcisoqqJtMoE8dhZ8k3oO1qWkBWE8YR mKIYWhV+VSA8xXPEymdpIDO+vC+mPbYOAWhAGzF0urNJaln10xIfprw98rV2gzHQ == X-ME-Sender: Received: from [10.7.33.159] (unknown [161.130.188.36]) by mail.messagingengine.com (Postfix) with ESMTPA id 7B096245F1; Mon, 26 Feb 2018 10:54:04 -0500 (EST) Subject: Re: [PATCH v3 6/7] arm64: allwinner: h6: add the basical Allwinner H6 DTSI file To: Maxime Ripard , Icenowy Zheng Cc: Chen-Yu Tsai , Linus Walleij , linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, linux-sunxi@googlegroups.com References: <20180223123555.64009-6-icenowy@aosc.io> <20180223123555.64009-7-icenowy@aosc.io> <20180223152038.2bflylwa6vj4gzfj@flea.lan> <81D53DC5-7622-430E-A530-ED0DE5397DC3@aosc.io> <20180226092645.xghkmfowenzlbm42@flea.lan> From: Samuel Holland Message-ID: Date: Mon, 26 Feb 2018 09:54:01 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180226092645.xghkmfowenzlbm42@flea.lan> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/26/18 03:26, Maxime Ripard wrote: > On Fri, Feb 23, 2018 at 11:22:06PM +0800, Icenowy Zheng wrote: >>>> + psci { >>>> + compatible = "arm,psci-0.2"; >>>> + method = "smc"; >>>> + }; >>> >>> Is it needed? The bootloader should fill it with whatever version it >>> has, shouldn't it? >> >> But we now use ATF rather than U-Boot PSCI. U-Boot will not fill ATF >> info. >> >> See A64/H5 device trees. > > So if the PSCI version implemented in ATF ever changes, we would have > to update all the DT everywhere, but only if you're running the new > version? Yes but no. PSCI 1.0 is generally backward compatible with PSCI 0.2. In fact, the Linux driver treats them exactly the same: { .compatible = "arm,psci-0.2", .data = psci_0_2_init}, { .compatible = "arm,psci-1.0", .data = psci_0_2_init}, For the H6, however, the oldest ATF source available (which I believe was the one in use during bringup) is based on mainline 1.4, and is already at PSCI version 1.1: [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not supported. So we could go ahead and bump the compatible to "arm,psci-1.0". Thanks, Samuel