linux-kernel - Re: [PATCH V3 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7hshtbtu8l.fsf@baylibre.com>
Date:   Wed, 07 Sep 2016 11:55:38 -0700
From:   Kevin Hilman <khilman@...libre.com>
To:     Nishanth Menon <nm@...com>
Cc:     Rob Herring <robh@...nel.org>, Tero Kristo <t-kristo@...com>,
        Santosh Shilimkar <ssantosh@...nel.org>,
        devicetree@...r.kernel.org, Dave Gerlach <d-gerlach@...com>,
        Lokesh Vutla <lokeshvutla@...com>, linux-pm@...r.kernel.org,
        linux-kernel@...r.kernel.org, "Andrew F . Davis" <afd@...com>,
        Russell King <rmk+kernel@...linux.org.uk>,
        Russ Dill <Russ.Dill@...com>,
        Sudeep Holla <sudeep.holla@....com>,
        linux-arm-kernel@...ts.infradead.org, narmstrong@...libre.com
Subject: Re: [PATCH V3 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver

Nishanth Menon <nm@...com> 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