Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2935609pxb; Tue, 19 Jan 2021 09:26:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJzWcIXRrIwKbj/vlnihjyUPIsaqQMkUU6dUpKgcO5Ll/+FtLARMqXFHLywuwqJl2H4+QTB7 X-Received: by 2002:a50:da8b:: with SMTP id q11mr4402660edj.352.1611077207533; Tue, 19 Jan 2021 09:26:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611077207; cv=none; d=google.com; s=arc-20160816; b=rm2y2PZC/WKLO8wYW11DeybjEQpq/cI03ZPTw68Bd5rHRo4af5L+Q+xf5rdsCsCdUO JpY56RgKNJHu1EkN3r3780Atj9rU+uR26LgqlmVzxZ9Ge9iQXwm/l1JjhbgoyONnxVsF XFrKwSrRhWtlZW6+ThbuNkeawby4P7JIcHt16qlcTne6Dqzo8EUm69mT4vFLlTC2TPO5 qKTo0y5eQ1xTlPn+dQw59TOMvU7syWCaFs4gAsNJeU97hPzMgtGBdz1A9LEzpPjUfq26 +VB+0f3CUi9XIPK9WNCRfjJE/SO0lCKZstK+zVdY40mEHmuAucpq4ESCdCfb7d6YMiTM xqQQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=eq3pibBJC/MIbQrmj5jtslhrZBYFdkd6st7vbpmB4rg=; b=I9aLXuctH18mGRA8S+kyERpMtFKH5tt/yN2iBgFxmq5XSC8d3eR+9ChXWpPH9WtGm0 KuhleehmsF49mXeP5pDisARPtFdK6+Yju+M6IzjMjDrvIYL9NSG2/4n1PaPsoCVEPS3d Ump4ziygjT8BXpESz6+bwgBYVgd7EnPf46DCPbCQr4mMjAein+/LHI2Yi2a1AyR5uSfM hFdFvRuBCUw3bRLlcy4Dte3cNTrQOsiOdmLJu17KjRcXAfsGXRvYIrDFIJR/M0bjSocw ZpAbjpEoNt+gbFBE+A6WuAwE/3q9kyxcc52lBY4CLQoMoF6C4zrlzuTt7BmiyuEHBoNc jVnw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m3si8511935ejn.166.2021.01.19.09.26.23; Tue, 19 Jan 2021 09:26:47 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390338AbhASRWt (ORCPT + 99 others); Tue, 19 Jan 2021 12:22:49 -0500 Received: from foss.arm.com ([217.140.110.172]:41292 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390373AbhASRVb (ORCPT ); Tue, 19 Jan 2021 12:21:31 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4745111D4; Tue, 19 Jan 2021 09:20:33 -0800 (PST) Received: from bogus (unknown [10.57.35.27]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 918BD3F66E; Tue, 19 Jan 2021 09:20:30 -0800 (PST) Date: Tue, 19 Jan 2021 17:20:28 +0000 From: Sudeep Holla To: "Zulkifli, Muhammad Husaini" Cc: Cristian Marussi , Mark Brown , "ulf.hansson@linaro.org" , "lgirdwood@gmail.com" , "robh+dt@kernel.org" , "devicetree@vger.kernel.org" , "Hunter, Adrian" , "michal.simek@xilinx.com" , "linux-mmc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "Shevchenko, Andriy" , "A, Rashmi" , "Vaidya, Mahesh R" Subject: Re: [PATCH v1 5/9] firmware: keembay: Add support for Trusted Firmware Service call Message-ID: <20210119172028.577x72bxv2khmg76@bogus> References: <20210118120132.GC25035@e120937-lin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171215 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 19, 2021 at 02:38:32AM +0000, Zulkifli, Muhammad Husaini wrote: [...] > > I try to hook up the DT last night. Seems like the SCMI Protocol 17 is not > implemented at ATF side. I had guessed that. > Double check with ATF Team, currently we don't have SCMI voltage domain > control in ARM Trusted Firmware yet as of now, that is why even if I map the > function to scmi, my call will be fail. Correct, but if you already have this custom SMCCC for voltage already implemented in TF-A, I don't see it is a big deal to support voltage protocol there. > > [ 2.648989] arm-scmi firmware:scmi: SCMI Notifications - Core Enabled. > [ 2.656157] arm-scmi firmware:scmi: SCMI Protocol v1.0 'INTEL:KMB' Firmware version 0x1 > [ 2.664513] arm-scmi firmware:scmi: SCMI protocol 23 not implemented > [ 2.675898] arm-scmi firmware:scmi: SCMI protocol 17 not implemented > > Any possibilities that for UHS patch we go with my current regulator driver > implementation? Sorry absolutely no. If this platform was not using SCMI, I wouldn't have pushed back hard on this custom SMCCC. Please update TF-A to add this support. There is no point in having custom interface just for this when everything else is already using SCMI on this platform. -- Regards, Sudeep