From: Kevin Hilman <khilman@baylibre.com>
To: Nishanth Menon <nm@ti.com>
Cc: Rob Herring <robh@kernel.org>, Tero Kristo <t-kristo@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
devicetree@vger.kernel.org, Dave Gerlach <d-gerlach@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andrew F . Davis" <afd@ti.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
Russ Dill <Russ.Dill@ti.com>, Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org, narmstrong@baylibre.com
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 [thread overview]
Message-ID: <7hshtbtu8l.fsf@baylibre.com> (raw)
In-Reply-To: <20160906190127.23522-1-nm@ti.com> (Nishanth Menon's message of "Tue, 6 Sep 2016 14:01:22 -0500")
Nishanth Menon <nm@ti.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
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [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 [thread overview]
Message-ID: <7hshtbtu8l.fsf@baylibre.com> (raw)
In-Reply-To: <20160906190127.23522-1-nm@ti.com> (Nishanth Menon's message of "Tue, 6 Sep 2016 14:01:22 -0500")
Nishanth Menon <nm@ti.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
next prev parent reply other threads:[~2016-09-07 18:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 19:01 [PATCH V3 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` [PATCH V3 1/5] Documentation: Add support for TI System Control Interface (TI-SCI) protocol Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-16 12:13 ` Rob Herring
2016-09-16 12:13 ` Rob Herring
2016-09-06 19:01 ` [PATCH V3 2/5] firmware: Add basic " Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` [PATCH V3 3/5] firmware: ti_sci: Add support for Device control Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
[not found] ` <20160906190127.23522-1-nm-l0cyMroinI0@public.gmane.org>
2016-09-06 19:01 ` [PATCH V3 4/5] firmware: ti_sci: Add support for Clock control Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` [PATCH V3 5/5] firmware: ti_sci: Add support for reboot core service Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-06 19:01 ` Nishanth Menon
2016-09-07 18:55 ` Kevin Hilman [this message]
2016-09-07 18:55 ` [PATCH V3 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver Kevin Hilman
2016-09-08 14:00 ` Nishanth Menon
2016-09-08 14:00 ` Nishanth Menon
2016-09-08 14:00 ` Nishanth Menon
2016-09-08 17:31 ` Kevin Hilman
2016-09-08 17:31 ` Kevin Hilman
2016-09-08 17:31 ` Kevin Hilman
2016-09-08 18:19 ` Tero Kristo
2016-09-08 18:19 ` Tero Kristo
2016-09-08 18:19 ` Tero Kristo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7hshtbtu8l.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Russ.Dill@ti.com \
--cc=afd@ti.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=narmstrong@baylibre.com \
--cc=nm@ti.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh@kernel.org \
--cc=ssantosh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=t-kristo@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.