From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 51BC769940; Fri, 1 Mar 2024 07:52:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709279529; cv=none; b=PanMgkZ7khkMVhLf9jDB7I3ke4TYIqpIZrXJC08wnZSLFJVdA6cbvECukXKLfHtHnN+LC5Mtj9gjj3s+AOdDjjG/qPkHmDnshdvATJZy7gJeOBdAkRhaG71liC0dKtVZURaIjsJ/Ze47NuahHLOdwXvYA3FcUFad27Wdh0bFZzI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1709279529; c=relaxed/simple; bh=5c4S5pDVGDNWPhl5plBFUkNQRRvMXFCw+sbpgEaM/Zo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=pKfWBHv9VObwL0MokKTPltB+N1WyFLPIMhotJCJ1hNK3mq9Ave/sbmwpJ0xmQJFhMYfOfofF/o7Qkk5fVs0/T6nC02tWQegy+TsyuF7WBx1vNrob/d3/ScWQJTiOGekGlK8I7sIuAAz0AcUZySSN8dQ00R5TimaR1VfNEP2r9xc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com 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 AEC551FB; Thu, 29 Feb 2024 23:52:44 -0800 (PST) Received: from pluto (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2BE7E3F762; Thu, 29 Feb 2024 23:52:05 -0800 (PST) Date: Fri, 1 Mar 2024 07:52:02 +0000 From: Cristian Marussi To: Peng Fan Cc: Sudeep Holla , "Peng Fan (OSS)" , "robh@kernel.org" , "krzysztof.kozlowski+dt@linaro.org" , "conor+dt@kernel.org" , "linux-arm-kernel@lists.infradead.org" , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] dt-bindings: firmware: arm,scmi: support system power protocol Message-ID: References: <20240226130243.3820915-1-peng.fan@oss.nxp.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Mar 01, 2024 at 12:41:29AM +0000, Peng Fan wrote: > > Subject: Re: [PATCH] dt-bindings: firmware: arm,scmi: support system power > > protocol > > > > On Tue, Feb 27, 2024 at 01:01:41AM +0000, Peng Fan wrote: > > > > Subject: Re: [PATCH] dt-bindings: firmware: arm,scmi: support system > > > > power protocol > > > > > > > > On Mon, Feb 26, 2024 at 01:28:31PM +0000, Cristian Marussi wrote: > > > > > On Mon, Feb 26, 2024 at 09:02:43PM +0800, Peng Fan (OSS) wrote: > > > > > > From: Peng Fan > > > > > > > > > > > > Add SCMI System Power Protocol bindings, and the protocol id is 0x12. > > > > > > > > > > > Hi, > > > > > > > > > > yes this is something I spotted in the past it was missing and I > > > > > posted a similar patch but I was told that a protocol node without > > > > > any specific additional properties is already being described by > > > > > the general protocol node described above. > > > > > > Without this patch, there is dtbs_check warning. > > > > > > scmi: 'protocol@12' does not match any of the regexes: 'pinctrl-[0-9]+' > > > from schema $id: > > > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdevic > > > > > etree.org%2Fschemas%2Ffirmware%2Farm%2Cscmi.yaml%23&data=05%7C0 > > 2%7Cpen > > > > > g.fan%40nxp.com%7Ccac77deb5f6a4b20460a08dc392ead40%7C686ea1d3b > > c2b4c6fa > > > > > 92cd99c5c301635%7C0%7C0%7C638448119832543335%7CUnknown%7CT > > WFpbGZsb3d8e > > > > > yJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D > > %7C0% > > > > > 7C%7C%7C&sdata=6MldIOUQ4hxn%2BRffwJJJ3jxXXtHCSxLUOa4JMWB0htU% > > 3D&reserv > > > ed=0 > > > > > > > Why are you adding protocol@12 to the device tree ? Does it have a > > dedicated channel ? If not, you shouldn't need to add it. > > No dedicated channel. > The idea is we have multile Agent, the M7 agent may ask to shutdown Linux > Agent. So the linux agent need use protocol@12 to do the action. > Ok, so indeed you need, AFAICR, the node in the DT even without a dedicated channel nor anynone referring it: no DT node means no protocol initialization. > For now, we have not finish implementing this in linux side, just add > the node in dts. On the linux side you should not need to do anything but adding the node @12, the existent drivers/firmware/arm_scmi/system_power_control.c driver when loaded will shutdown the system upon receiving the SytemPower notification....what lacks Linux side in these regards ? Thanks, Cristian