Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp222549pxb; Fri, 15 Jan 2021 11:16:52 -0800 (PST) X-Google-Smtp-Source: ABdhPJzRoWCak1Hhyh2yRLgoatvPYZ0K2oO7A1yVT3iK8uSw2zS69OTsTZa8Lyf5EXDh3foPrAgh X-Received: by 2002:a17:906:f88f:: with SMTP id lg15mr357174ejb.70.1610738212647; Fri, 15 Jan 2021 11:16:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610738212; cv=none; d=google.com; s=arc-20160816; b=Mi1MeZ2vhl4RJqipyf0z0kQybceockuR89VB89ntmDrujKaf8i5c7ZuY+46I3TlTFc tbWWwiFHZkPaPRKZySUDjLZz5FEPACaaeDSzruXoTRurO0rqLraVHmAtGqI9MAOsSfLy sUacQn7Es0KpS9e+/aAUMCrzjxcvBVlvJch5aVmLcDqFPlKbISI2Zhx9+NGP/mofTKQg UGJuvhFeWwvwZhbM3or63PX20gn/yhAkYguX5HHmUz/JP+ZKxc80LACj3gv26/WMM24B zbg8YDVSpuzNM0Lildob0d66SgJk2VcQ5iSfLEM2o6+rioNqrvg/qbVoGYhTQJbdmzhR mQ7w== 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=44N715NgAV2kUSxfYHsbKE2n/C3bzu8ZmjGHF9YfJqw=; b=0GWwuGdrKbQxmo5MFxdfyWgV9HuRy/v9hUMPLk+t5J1aKQQR7NBCst7sRWxChDMe4h x6F19nH6ccp6ZcRZIJ0OaHOKWIck1npuM2Fil/1f8S883fKvYbY4GE7a0iLm743N0bKA /Fn+7ClAoe8F+p9+MVFiV8/3i2oMw/1dChd3yHxC5glm+3zGUKDewwHQo2PMOe+JJl4t +BZ9fez0NjtSgho6418lw4Ljx5si2mo8J3XHDqu1GnuyoGSfGDq6SKAm0/admrJdgAtc PoBGjctPlZPxij1Qp0tqRhAHnj3srJBzRYjjFykzRFhNBHBYVwuu1tRp3Rc4CkrSJMcd 9m8g== 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 f21si4729722edr.152.2021.01.15.11.16.28; Fri, 15 Jan 2021 11:16:52 -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 S2388361AbhAOTPR (ORCPT + 99 others); Fri, 15 Jan 2021 14:15:17 -0500 Received: from foss.arm.com ([217.140.110.172]:52484 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388123AbhAOTPQ (ORCPT ); Fri, 15 Jan 2021 14:15:16 -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 C28C7ED1; Fri, 15 Jan 2021 11:14:30 -0800 (PST) Received: from bogus (unknown [10.57.35.27]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id BFF393F719; Fri, 15 Jan 2021 11:14:28 -0800 (PST) Date: Fri, 15 Jan 2021 19:14:26 +0000 From: Sudeep Holla To: Mark Brown Cc: Muhammad Husaini Zulkifli , ulf.hansson@linaro.org, lgirdwood@gmail.com, robh+dt@kernel.org, devicetree@vger.kernel.org, adrian.hunter@intel.com, michal.simek@xilinx.com, linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, andriy.shevchenko@intel.com, Rashmi.A@intel.com, mahesh.r.vaidya@intel.com, Sudeep Holla Subject: Re: [PATCH v1 8/9] regulator: keembay: Add regulator for Keem Bay SoC Message-ID: <20210115191426.xf23pde2drtlujkg@bogus> References: <20210114152700.21916-1-muhammad.husaini.zulkifli@intel.com> <20210114152700.21916-9-muhammad.husaini.zulkifli@intel.com> <20210114171434.GI4854@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210114171434.GI4854@sirena.org.uk> User-Agent: NeoMutt/20171215 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 14, 2021 at 05:14:34PM +0000, Mark Brown wrote: > On Thu, Jan 14, 2021 at 11:26:59PM +0800, Muhammad Husaini Zulkifli wrote: > > > Keem Bay SD regulator driver module is added to encapsulate ARM > > Secure Monitor Call Calling Convention (SMCCC) during set voltage > > operations to control I/O Rail supplied voltage levels which communicate > > with Trusted Firmware. > > Adding in Sudeep again for the SMCCC bits. I just checked and am I > right in thinking this might already be shipping in production? > OK you seem to have asked the most important question here directly. I have asked for the details of platform firmware implementation in the other email basically for the same reason(to check how feasible is it to move to new SCMI voltage protocol). Some work in the firmware, but if the implement is on the A-profile itself in TF-A or any other equivalent, it should not be too difficult. -- Regards, Sudeep