Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp6033737ybx; Mon, 11 Nov 2019 02:47:10 -0800 (PST) X-Google-Smtp-Source: APXvYqz9eRDMV9wkMtBWgjjy6/vV5KYdbrYYspbbqPG5Cs84YN2VxBRMVaQElvrlNJ6TAh0xJz6z X-Received: by 2002:a17:906:194a:: with SMTP id b10mr22205400eje.123.1573469230495; Mon, 11 Nov 2019 02:47:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573469230; cv=none; d=google.com; s=arc-20160816; b=ofN5Quzx2YL2oFCcoyPtxhx2ZAimYFag5s+c570IcvRvLWqK3t/6slc8eoE0KehrFz FmU2P0NURwmP1rfQPpipLr2XT2/5sPoB30JvFBJ7RIBr6HD5gnOx9+yE0YyQCyQ5W+3y m2QFgqx9DYp9P+X42d6AaabAfiLAOK8+UtQEQjB3ZI6Znr7T2gz8b2awmC5lSJRNbCBh fCXP37/DqmNhxzkO9dPLmT5hp1TxvFhZpiq9NntDakuIs/rru7miDO16Uf4CW+V39trO CbtNM7bwWy1a60qbxO+JAZLxpNhyqiUwdi2SLp7TuS44QXCNznZwuSeFCKiz6kAzJgWP /yUQ== 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; bh=HX7IYa/GFMe344d0JL5pWdN+Xsutc4yU/MnqlbTkYAU=; b=KGc3gajiaQjbSc+NLkcVeaigYI9pQYXDNPcDpcq/o3092KbbTYtsLCyOYI55rms8Zc tLrbRepJzYUreMI18ETzcdAeiInihrXMZJ4J9VWS6BwjtWUTXlk2sK0HIzVwDrhmWLqB jy2OACnlSUDHAvbfY6ybmdiVTM8506s3cZQMigkQ2WHLrb76HySkj8LxpqsLBkvDgy3a RZvgaAOiLZRllTluPJumULpp8D1aqU80BGs7IJWuj526kwVp6J5xECqAUEriHLYcosZe 8KpUhcW2w9HE1VgbSjl8ikFXa3texhSVjWNiUi8XBnMg3LaJBk0r9h4rkO4Q3Hn0M7N9 avMQ== ARC-Authentication-Results: i=1; mx.google.com; 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 k15si9484889ejc.331.2019.11.11.02.46.47; Mon, 11 Nov 2019 02:47:10 -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; 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 S1726928AbfKKKpp (ORCPT + 99 others); Mon, 11 Nov 2019 05:45:45 -0500 Received: from mail-sh.amlogic.com ([58.32.228.43]:34933 "EHLO mail-sh.amlogic.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726829AbfKKKpp (ORCPT ); Mon, 11 Nov 2019 05:45:45 -0500 Received: from [10.18.29.227] (10.18.29.227) by mail-sh.amlogic.com (10.18.11.5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1591.10; Mon, 11 Nov 2019 18:46:03 +0800 Subject: Re: [PATCH v4 2/4] firmware: meson_sm: Add secure power domain support To: Kevin Hilman , CC: Rob Herring , Neil Armstrong , Jerome Brunet , Martin Blumenstingl , , , , , Jian Hu , Hanjie Lin , Victor Wan , Xingyu Chen References: <1572868028-73076-1-git-send-email-jianxin.pan@amlogic.com> <1572868028-73076-3-git-send-email-jianxin.pan@amlogic.com> <7hk188stcy.fsf@baylibre.com> From: Jianxin Pan Message-ID: <420073b1-0a3f-1bfd-4422-34f8cd7e0d2d@amlogic.com> Date: Mon, 11 Nov 2019 18:46:03 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <7hk188stcy.fsf@baylibre.com> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.18.29.227] X-ClientProxiedBy: mail-sh.amlogic.com (10.18.11.5) To mail-sh.amlogic.com (10.18.11.5) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Kevin, Please see my comments below: On 2019/11/10 4:11, Kevin Hilman wrote: > Jianxin Pan writes: > >> The Amlogic Meson A1/C1 Secure Monitor implements calls to control power >> domain. >> >> Signed-off-by: Jianxin Pan >> --- >> drivers/firmware/meson/meson_sm.c | 2 ++ >> include/linux/firmware/meson/meson_sm.h | 2 ++ >> 2 files changed, 4 insertions(+) >> [...] >> diff --git a/include/linux/firmware/meson/meson_sm.h b/include/linux/firmware/meson/meson_sm.h >> index 6669e2a..4ed3989 100644 >> --- a/include/linux/firmware/meson/meson_sm.h >> +++ b/include/linux/firmware/meson/meson_sm.h >> @@ -12,6 +12,8 @@ enum { >> SM_EFUSE_WRITE, >> SM_EFUSE_USER_MAX, >> SM_GET_CHIP_ID, >> + SM_PWRC_SET, >> + SM_PWRC_GET, > > These new IDs are unique to the A1/C1 family. Maybe we should add a > prefix to better indicate that. Maybe: > > SM_A1_PWRC_SET, > SM_A1_PWRC_GET, > > Thoughts? > I consulted with the internal VLSI team, and it's likely that the latter new SOC will follow A1/C1. And then it may become common function in the future. > Kevin > > . >