public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>,
	David Griego <david.griego@linaro.org>
Subject: Re: [PATCH V3 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver
Date: Thu, 08 Sep 2016 10:31:03 -0700	[thread overview]
Message-ID: <m2y432nvs8.fsf@baylibre.com> (raw)
In-Reply-To: <f41d968c-46c9-997e-0fa0-edbef34a1fa5@ti.com> (Nishanth Menon's message of "Thu, 8 Sep 2016 09:00:37 -0500")

Nishanth Menon <nm@ti.com> writes:

> On 09/07/2016 01:55 PM, Kevin Hilman wrote:
>> Nishanth Menon <nm@ti.com> writes:
>
> [...] full mail thread in https://lkml.org/lkml/2016/9/6/747
>
>>> 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.

[...]

> Long story short, investigation was done into what SCPI was providing
> (TI internal ofcourse) and SCPI did not fit our SoC generation needs -

Thanks for the detailed explanation.  Very helpful.

To be clear, I'm not a proponent of always using ARM "standards"
(especially when it's not exactly clear if it's a standard or a Juno
thing) but I'm seeing several SoCs come out with SCPI derivatives, or
old ARM versions etc., so was just curious about the decision making
process.

Thanks for sharing,

Kevin

  reply	other threads:[~2016-09-08 17:31 UTC|newest]

Thread overview: 11+ 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 ` [PATCH V3 1/5] Documentation: Add support for TI System Control Interface (TI-SCI) protocol Nishanth Menon
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 ` [PATCH V3 3/5] firmware: ti_sci: Add support for Device control Nishanth Menon
2016-09-06 19:01 ` [PATCH V3 4/5] firmware: ti_sci: Add support for Clock control Nishanth Menon
2016-09-06 19:01 ` [PATCH V3 5/5] firmware: ti_sci: Add support for reboot core service Nishanth Menon
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 17:31     ` Kevin Hilman [this message]
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=m2y432nvs8.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=Charles.Garcia-Tobin@arm.com \
    --cc=Russ.Dill@ti.com \
    --cc=afd@ti.com \
    --cc=d-gerlach@ti.com \
    --cc=david.griego@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox