From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <nm@ti.com>, <t-kristo@ti.com>, <ssantosh@kernel.org>,
<lokeshvutla@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <grygorii.strashko@ti.com>
Subject: [PATCH v2 00/11] firmware/soc: ti_sci, ringacc/inta: Preparation for AM64 DMA support
Date: Thu, 8 Oct 2020 14:52:13 +0300 [thread overview]
Message-ID: <20201008115224.1591-1-peter.ujfalusi@ti.com> (raw)
Hi,
Changes since v1:
- Use AM64X as family name in patch 11
- Added Reviewed-by tag from Grygorii for patch 6-10
The series prepares the ti_sci, ringacc, inta to support the new DMAs introduced
with AM64.
Separate series has been sent for the inta irqchip driver (v2):
https://lore.kernel.org/lkml/20200930074559.18028-1-peter.ujfalusi@ti.com/
Patches for the DMA support will be based on this series due to build and
feature dependencies.
To support the new DMSS we need to change the ti_sci ring config API in order to
be able to support the new parameters needed in the future.
We also need to add support for the second range in RM as along with the AM64
support, the resource allocation is going to change for existing SoC which used
only the first range for resource allocation.
The tx_tdtype support has been also missing from ti_sci for a long time and
the AM64 specific extended_ch_type depends on the existence of it in the message
struct.
Santosh: if you plan to take this series for 5.11, then can you create an
immutable branch which I can refer to Vinod for the DMA patches I'm going to
send soon.
Regards,
Peter
---
Peter Ujfalusi (11):
firmware: ti_sci: rm: Add support for tx_tdtype parameter for tx
channel
firmware: ti_sci: Use struct ti_sci_resource_desc in get_range ops
firmware: ti_sci: rm: Add support for second resource range
soc: ti: ti_sci_inta_msi: Add support for second range in resource
ranges
firmware: ti_sci: rm: Add support for extended_ch_type for tx channel
firmware: ti_sci: rm: Remove ring_get_config support
firmware: ti_sci: rm: Add new ops for ring configuration
soc: ti: k3-ringacc: Use the ti_sci set_cfg callback for ring
configuration
firmware: ti_sci: rm: Remove unused config() from
ti_sci_rm_ringacc_ops
soc: ti: k3-ringacc: Use correct device for allocation in RING mode
soc: ti: k3-socinfo: Add entry for AM64X SoC family
drivers/firmware/ti_sci.c | 213 ++++++++-----------------
drivers/firmware/ti_sci.h | 72 +++------
drivers/soc/ti/k3-ringacc.c | 93 +++++------
drivers/soc/ti/k3-socinfo.c | 1 +
drivers/soc/ti/ti_sci_inta_msi.c | 12 ++
include/linux/soc/ti/k3-ringacc.h | 5 +
include/linux/soc/ti/ti_sci_protocol.h | 85 ++++++----
7 files changed, 212 insertions(+), 269 deletions(-)
--
Peter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next reply other threads:[~2020-10-08 11:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 11:52 Peter Ujfalusi [this message]
2020-10-08 11:52 ` [PATCH v2 01/11] firmware: ti_sci: rm: Add support for tx_tdtype parameter for tx channel Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 02/11] firmware: ti_sci: Use struct ti_sci_resource_desc in get_range ops Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 03/11] firmware: ti_sci: rm: Add support for second resource range Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 04/11] soc: ti: ti_sci_inta_msi: Add support for second range in resource ranges Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 05/11] firmware: ti_sci: rm: Add support for extended_ch_type for tx channel Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 06/11] firmware: ti_sci: rm: Remove ring_get_config support Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 07/11] firmware: ti_sci: rm: Add new ops for ring configuration Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 08/11] soc: ti: k3-ringacc: Use the ti_sci set_cfg callback " Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 09/11] firmware: ti_sci: rm: Remove unused config() from ti_sci_rm_ringacc_ops Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 10/11] soc: ti: k3-ringacc: Use correct device for allocation in RING mode Peter Ujfalusi
2020-10-09 3:02 ` Nishanth Menon
2020-10-09 7:43 ` Peter Ujfalusi
2020-10-09 11:59 ` Nishanth Menon
2020-10-09 12:10 ` Peter Ujfalusi
2020-10-08 11:52 ` [PATCH v2 11/11] soc: ti: k3-socinfo: Add entry for AM64X SoC family Peter Ujfalusi
2020-10-09 0:54 ` [PATCH v2 00/11] firmware/soc: ti_sci, ringacc/inta: Preparation for AM64 DMA support santosh.shilimkar
2020-10-09 0:56 ` santosh.shilimkar
2020-10-09 8:08 ` Peter Ujfalusi
2020-11-02 3:44 ` santosh.shilimkar
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=20201008115224.1591-1-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--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=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
all inboxes | Powered by JetHome®