From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH V3 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver Date: Wed, 07 Sep 2016 11:55:38 -0700 Message-ID: <7hshtbtu8l.fsf@baylibre.com> References: <20160906190127.23522-1-nm@ti.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mail-pf0-f176.google.com ([209.85.192.176]:33602 "EHLO mail-pf0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755991AbcIGSzl (ORCPT ); Wed, 7 Sep 2016 14:55:41 -0400 Received: by mail-pf0-f176.google.com with SMTP id g202so9392997pfb.0 for ; Wed, 07 Sep 2016 11:55:40 -0700 (PDT) In-Reply-To: <20160906190127.23522-1-nm@ti.com> (Nishanth Menon's message of "Tue, 6 Sep 2016 14:01:22 -0500") Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: Nishanth Menon Cc: Rob Herring , Tero Kristo , Santosh Shilimkar , devicetree@vger.kernel.org, Dave Gerlach , Lokesh Vutla , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, "Andrew F . Davis" , Russell King , Russ Dill , Sudeep Holla , linux-arm-kernel@lists.infradead.org, narmstrong@baylibre.com Nishanth Menon writes: > Hi, > > Version 3 of the series with change in the way we describe the children > nodes (no change to drivers required - only the dts description changes). > > Texas Instruments' Keystone generation System on Chips (SoC) > starting with 66AK2G02[1], now include a dedicated SoC System Control > entity called PMMC(Power Management Micro Controller) in line with > ARM architecture recommendations. The function of this module is > to integrate all system operations in a centralized location. > Communication with the SoC System Control entity from various > processing units like ARM/DSP occurs over Message Manager hardware > block. > > This series adds the base support for TI System Control Interface > (TI-SCI) protocol[2]. The protocol is built on top of Texas > Instrument's Message Manager communication mechanism[3]. > > Overall architecture is very similar to SCPI[4] as follows: Dumb Q: I'm curious about the limitations in SCPI that were found that made TI decided to implement its own version. Thanks, Kevin From mboxrd@z Thu Jan 1 00:00:00 1970 From: khilman@baylibre.com (Kevin Hilman) Date: Wed, 07 Sep 2016 11:55:38 -0700 Subject: [PATCH V3 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver In-Reply-To: <20160906190127.23522-1-nm@ti.com> (Nishanth Menon's message of "Tue, 6 Sep 2016 14:01:22 -0500") References: <20160906190127.23522-1-nm@ti.com> Message-ID: <7hshtbtu8l.fsf@baylibre.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Nishanth Menon writes: > Hi, > > Version 3 of the series with change in the way we describe the children > nodes (no change to drivers required - only the dts description changes). > > Texas Instruments' Keystone generation System on Chips (SoC) > starting with 66AK2G02[1], now include a dedicated SoC System Control > entity called PMMC(Power Management Micro Controller) in line with > ARM architecture recommendations. The function of this module is > to integrate all system operations in a centralized location. > Communication with the SoC System Control entity from various > processing units like ARM/DSP occurs over Message Manager hardware > block. > > This series adds the base support for TI System Control Interface > (TI-SCI) protocol[2]. The protocol is built on top of Texas > Instrument's Message Manager communication mechanism[3]. > > Overall architecture is very similar to SCPI[4] as follows: Dumb Q: I'm curious about the limitations in SCPI that were found that made TI decided to implement its own version. Thanks, Kevin