From: Tero Kristo <t-kristo@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>, <vkoul@kernel.org>,
<nm@ti.com>, <ssantosh@kernel.org>
Cc: <dan.j.williams@intel.com>, <dmaengine@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <grygorii.strashko@ti.com>,
<tony@atomide.com>
Subject: Re: [PATCH v1.1] firmware: ti_sci: Add resource management APIs for ringacc, psi-l and udma
Date: Tue, 11 Jun 2019 20:36:12 +0300 [thread overview]
Message-ID: <2a755211-afd9-070c-954c-f6f2d931455b@ti.com> (raw)
In-Reply-To: <636f599a-cefa-ce70-d0ae-b5244edf14b2@ti.com>
On 10/06/2019 12:41, Lokesh Vutla wrote:
>
>
> On 10/06/19 2:48 PM, Peter Ujfalusi wrote:
>> Configuration of NAVSS resource, like rings, UDMAP channels, flows
>> and PSI-L thread management need to be done via TISCI.
>>
>> Add the needed structures and functions for NAVSS resource configuration of
>> the following:
>> Rings from Ring Accelerator
>> PSI-L thread management
>> UDMAP tchan, rchan and rflow configuration.
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
>
> Thanks and regards,
> Lokesh
>
Thanks, queuing this single patch up for 5.3.
Vinod, I am setting up an immutable branch if you need to pick this
patch up; basically if you are planning to merge the dma support for
5.3. Available as a tag here (I'll send a pull-req out for this in a bit):
git://git.kernel.org/pub/scm/linux/kernel/git/kristo/linux
tags/ti-sci-for-5.3
It is based on top of clock driver pull-request due to dependencies.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
WARNING: multiple messages have this Message-ID (diff)
From: Tero Kristo <t-kristo@ti.com>
To: Lokesh Vutla <lokeshvutla@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>, <vkoul@kernel.org>,
<nm@ti.com>, <ssantosh@kernel.org>
Cc: grygorii.strashko@ti.com, tony@atomide.com,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
dan.j.williams@intel.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1.1] firmware: ti_sci: Add resource management APIs for ringacc, psi-l and udma
Date: Tue, 11 Jun 2019 20:36:12 +0300 [thread overview]
Message-ID: <2a755211-afd9-070c-954c-f6f2d931455b@ti.com> (raw)
In-Reply-To: <636f599a-cefa-ce70-d0ae-b5244edf14b2@ti.com>
On 10/06/2019 12:41, Lokesh Vutla wrote:
>
>
> On 10/06/19 2:48 PM, Peter Ujfalusi wrote:
>> Configuration of NAVSS resource, like rings, UDMAP channels, flows
>> and PSI-L thread management need to be done via TISCI.
>>
>> Add the needed structures and functions for NAVSS resource configuration of
>> the following:
>> Rings from Ring Accelerator
>> PSI-L thread management
>> UDMAP tchan, rchan and rflow configuration.
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
>
> Thanks and regards,
> Lokesh
>
Thanks, queuing this single patch up for 5.3.
Vinod, I am setting up an immutable branch if you need to pick this
patch up; basically if you are planning to merge the dma support for
5.3. Available as a tag here (I'll send a pull-req out for this in a bit):
git://git.kernel.org/pub/scm/linux/kernel/git/kristo/linux
tags/ti-sci-for-5.3
It is based on top of clock driver pull-request due to dependencies.
-Tero
--
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
next prev parent reply other threads:[~2019-06-11 17:36 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 12:34 [PATCH 00/16] dmaengine/soc/firmware: Add Texas Instruments UDMA support Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 01/16] firmware: ti_sci: Add resource management APIs for ringacc, psi-l and udma Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-06-06 6:00 ` Lokesh Vutla
2019-06-06 6:00 ` Lokesh Vutla
2019-06-06 6:00 ` Lokesh Vutla
2019-06-06 12:04 ` Peter Ujfalusi
2019-06-06 12:04 ` Peter Ujfalusi
2019-06-06 12:04 ` Peter Ujfalusi
2019-06-10 9:18 ` [PATCH v1.1] " Peter Ujfalusi
2019-06-10 9:18 ` Peter Ujfalusi
2019-06-10 9:41 ` Lokesh Vutla
2019-06-10 9:41 ` Lokesh Vutla
2019-06-11 17:36 ` Tero Kristo [this message]
2019-06-11 17:36 ` Tero Kristo
2019-05-06 12:34 ` [PATCH 02/16] bindings: soc: ti: add documentation for k3 ringacc Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-06-13 18:09 ` Rob Herring
2019-06-13 18:09 ` Rob Herring
2019-05-06 12:34 ` [PATCH 03/16] soc: ti: k3: add navss ringacc driver Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 04/16] dmaengine: doc: Add sections for per descriptor metadata support Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 05/16] dmaengine: Add metadata_ops for dma_async_tx_descriptor Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 06/16] dmaengine: Add support for reporting DMA cached data amount Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 07/16] dmaengine: Add function to request slave channel from a dma_device Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-07 8:37 ` Peter Ujfalusi
2019-05-07 8:37 ` Peter Ujfalusi
2019-05-07 8:37 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 08/16] dmaengine: ti: Add cppi5 header for UDMA Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 09/16] dt-bindings: dma: ti: Add document for K3 UDMA Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-06-13 18:16 ` Rob Herring
2019-06-13 18:16 ` Rob Herring
2019-06-13 20:33 ` Peter Ujfalusi
2019-06-13 20:33 ` Peter Ujfalusi
2019-06-13 20:33 ` Peter Ujfalusi
2019-06-14 13:20 ` Rob Herring
2019-06-14 13:20 ` Rob Herring
2019-06-14 13:20 ` Rob Herring
2019-06-14 13:43 ` Peter Ujfalusi
2019-06-14 13:43 ` Peter Ujfalusi
2019-06-14 13:43 ` Peter Ujfalusi
2019-06-19 14:04 ` Rob Herring
2019-06-19 14:04 ` Rob Herring
2019-06-19 14:04 ` Rob Herring
2019-06-20 9:56 ` Peter Ujfalusi
2019-06-20 9:56 ` Peter Ujfalusi
2019-06-20 9:56 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 10/16] dmaengine: ti: New driver for K3 UDMA - split#1: defines, structs, io func Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-06-13 18:43 ` Rob Herring
2019-06-13 18:43 ` Rob Herring
2019-06-13 20:40 ` Peter Ujfalusi
2019-06-13 20:40 ` Peter Ujfalusi
2019-06-13 20:40 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 11/16] dmaengine: ti: New driver for K3 UDMA - split#2: probe/remove, xlate and filter_fn Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 12/16] dmaengine: ti: New driver for K3 UDMA - split#3: alloc/free chan_resources Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 13/16] dmaengine: ti: New driver for K3 UDMA - split#4: dma_device callbacks 1 Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 14/16] dmaengine: ti: New driver for K3 UDMA - split#5: dma_device callbacks 2 Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 15/16] dmaengine: ti: New driver for K3 UDMA - split#6: Kconfig and Makefile Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` [PATCH 16/16] dmaengine: ti: k3-udma: Add glue layer for non DMAengine users Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
2019-05-06 12:34 ` Peter Ujfalusi
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=2a755211-afd9-070c-954c-f6f2d931455b@ti.com \
--to=t-kristo@ti.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.com \
--cc=vkoul@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 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.