From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver
Date: Thu, 27 Oct 2016 20:46:30 +0300 [thread overview]
Message-ID: <f51516ba-9539-78ca-1d40-585ece047ea0@ti.com> (raw)
In-Reply-To: <m260odhjcb.fsf@baylibre.com>
On 27/10/16 19:01, Kevin Hilman wrote:
> Tero Kristo <t-kristo@ti.com> writes:
>
>> On 19/10/16 02:08, Nishanth Menon wrote:
>>> Version 4 of the series is basically a rebase to v4.9-rc1, no functional
>>> changes.
>>
>> Any final comments on this series, or shall I send a pull-req forward?
>> Very minimal changes compared to v3 so should be good to go imo.
>
> Not a comment on the series, but a question on TI-SCI.
>
> Will the uC firmware be open like it was on AM335x?
Currently it seems like it will be closed. :(
-Tero
prev parent reply other threads:[~2016-10-27 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 23:08 [PATCH V4 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver Nishanth Menon
2016-10-18 23:08 ` [PATCH V4 1/5] Documentation: Add support for TI System Control Interface (TI-SCI) protocol Nishanth Menon
2016-10-18 23:08 ` [PATCH V4 2/5] firmware: Add basic " Nishanth Menon
2016-10-18 23:08 ` [PATCH V4 3/5] firmware: ti_sci: Add support for Device control Nishanth Menon
2016-10-18 23:08 ` [PATCH V4 4/5] firmware: ti_sci: Add support for Clock control Nishanth Menon
2016-10-18 23:08 ` [PATCH V4 5/5] firmware: ti_sci: Add support for reboot core service Nishanth Menon
2016-10-25 17:34 ` [PATCH V4 0/5] firmware: Add support for TI System Control Interface (TI-SCI) protocol driver Tero Kristo
2016-10-26 19:56 ` Santosh Shilimkar
2016-10-27 17:47 ` Tero Kristo
2016-10-27 16:01 ` Kevin Hilman
2016-10-27 17:46 ` Tero Kristo [this message]
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=f51516ba-9539-78ca-1d40-585ece047ea0@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).