devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <t-kristo@ti.com>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [GIT PULL] firmware: add support for TI System Control Interface (TI-SCI) protocol driver
Date: Fri, 2 Sep 2016 10:05:53 -0700	[thread overview]
Message-ID: <4586973c-603b-b37a-d32f-c2bc5310e589@oracle.com> (raw)
In-Reply-To: <CAGo_u6rXd9=664xhVkvrtEymD=4LF1KbCj+go_Vnyv6t5j963w@mail.gmail.com>

On 9/2/2016 10:03 AM, Nishanth Menon wrote:
> On Thu, Sep 1, 2016 at 2:24 AM, Tero Kristo <t-kristo@ti.com> wrote:
>> Hi Santosh,
>>
>> The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:
>>
>>   Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)
>>
>> are available in the git repository at:
>>
>>   https://github.com/t-kristo/linux-pm.git 4.8-rc1-ti-sci-fw
>>
>> for you to fetch changes up to 7a2c510cdfa6a4b2f4200c122a377c4d5f4af552:
>>
>>   firmware: ti_sci: Add support for reboot core service (2016-08-31 14:50:20
>> +0300)
>>
>> ----------------------------------------------------------------
>> Nishanth Menon (5):
>>       Documentation: Add support for TI System Control Interface (TI-SCI)
>> protocol
>>       firmware: Add basic support for TI System Control Interface (TI-SCI)
>> protocol
>>       firmware: ti_sci: Add support for Device control
>>       firmware: ti_sci: Add support for Clock control
>>       firmware: ti_sci: Add support for reboot core service
>>
>>  .../devicetree/bindings/arm/keystone/ti,sci.txt    |   66 +
>>  MAINTAINERS                                        |   10 +
>>  drivers/firmware/Kconfig                           |   15 +
>>  drivers/firmware/Makefile                          |    1 +
>>  drivers/firmware/ti_sci.c                          | 1997
>> ++++++++++++++++++++
>>  drivers/firmware/ti_sci.h                          |  492 +++++
>>  include/linux/soc/ti/ti_sci_protocol.h             |  249 +++
>>  7 files changed, 2830 insertions(+)
>>  create mode 100644
>> Documentation/devicetree/bindings/arm/keystone/ti,sci.txt
>>  create mode 100644 drivers/firmware/ti_sci.c
>>  create mode 100644 drivers/firmware/ti_sci.h
>>  create mode 100644 include/linux/soc/ti/ti_sci_protocol.h
>>
>
> Folks, could you hold back on this pull request.. Rob did have a
> comment on https://patchwork.kernel.org/patch/9305413/ which I think
> should be discussed as well -> has implications to the driver arch
> ofcourse.
>
Sure !!

      reply	other threads:[~2016-09-02 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01  7:24 [GIT PULL] firmware: add support for TI System Control Interface (TI-SCI) protocol driver Tero Kristo
2016-09-02 17:03 ` Nishanth Menon
2016-09-02 17:05   ` Santosh Shilimkar [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=4586973c-603b-b37a-d32f-c2bc5310e589@oracle.com \
    --to=santosh.shilimkar@oracle.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=nm@ti.com \
    --cc=ssantosh@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).