From: Tero Kristo <t-kristo@ti.com>
To: <santosh.shilimkar@oracle.com>, Suman Anna <s-anna@ti.com>,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] firmware: ti_sci: Add support for processor control
Date: Tue, 11 Jun 2019 20:37:01 +0300 [thread overview]
Message-ID: <a3eba154-d47f-1b2f-a2c6-9cb7a0ee817a@ti.com> (raw)
In-Reply-To: <ea3bf059-86b0-2d8c-c42d-44c08a6ec808@oracle.com>
On 10/06/2019 20:16, santosh.shilimkar@oracle.com wrote:
>
>
> On 6/10/19 5:19 AM, Tero Kristo wrote:
>> On 08/06/2019 00:35, santosh.shilimkar@oracle.com wrote:
>>> On 6/5/19 3:33 PM, Suman Anna wrote:
>>>> Texas Instrument's System Control Interface (TI-SCI) Message Protocol
>>>> is used in Texas Instrument's System on Chip (SoC) such as those
>>>> in K3 family AM654 SoC to communicate between various compute
>>>> processors with a central system controller entity.
>>>>
>>>> The system controller provides various services including the control
>>>> of other compute processors within the SoC. Extend the TI-SCI protocol
>>>> support to add various TI-SCI commands to invoke services associated
>>>> with power and reset control, and boot vector management of the
>>>> various compute processors from the Linux kernel.
>>>>
>>>> Signed-off-by: Suman Anna <s-anna@ti.com>
>>>> ---
>>>> Hi Santosh, Nishanth, Tero,
>>>>
>>>> Appreciate it if this patch can be picked up for the 5.3 merge window.
>>>> This is a dependency patch for my various remoteproc drivers on TI K3
>>>> SoCs. Patch is on top of v5.2-rc1.
>>>>
>>> I will pick this up for 5.3.
>>
>> Santosh,
>>
>> There is a pile of drivers/firmware changes for ti-sci, which have
>> cross dependencies, and will cause merge conflicts also as they touch
>> same file.
>>
>> Do you mind if I setup a pull-request for these all and send it to
>> you? They are going to be on top of the keystone clock pull-request I
>> just sent today though, otherwise it won't compile (the 32bit clock
>> support has dependency towards the clock driver.)
>>
> That will be great Tero.
Ok doing that.
For this patch, queuing up for 5.3, thanks.
-Tero
>
> Regards,
> Santosh
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-11 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 22:33 [PATCH] firmware: ti_sci: Add support for processor control Suman Anna
2019-06-06 4:04 ` Lokesh Vutla
2019-06-07 21:35 ` santosh.shilimkar
2019-06-10 12:19 ` Tero Kristo
2019-06-10 17:16 ` santosh.shilimkar
2019-06-11 17:37 ` 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=a3eba154-d47f-1b2f-a2c6-9cb7a0ee817a@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=s-anna@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.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).