From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Tero Kristo <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
<santosh.shilimkar@oracle.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
Rob Herring <robh+dt@kernel.org>, Sekhar Nori <nsekhar@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: [RESEND PATCH next v2 0/2] soc: ti: k3: ringacc: add am65x sr2.0 support
Date: Wed, 9 Sep 2020 22:43:36 +0300 [thread overview]
Message-ID: <20200909194338.21840-1-grygorii.strashko@ti.com> (raw)
soc: ti: k3: ringacc: add am65x sr2.0 support
Hi Santosh,
This is re-send of v2 with DT patch dropped.
---
This series adds support for the TI AM65x SR2.0 SoC Ringacc which has fixed
errata i2023 "RINGACC, UDMA: RINGACC and UDMA Ring State Interoperability
Issue after Channel Teardown". This errata also fixed for J271E SoC.
The SOC bus chipinfo data is used to identify the SoC and configure
i2023 errata W/A.
This changes made "ti,dma-ring-reset-quirk" DT property obsolete, so it's removed.
Changes in v2:
- no functional changes
- rebased on top of linux-next
- added ask from Rob Herring
v2: https://lore.kernel.org/patchwork/cover/1297255/
v1: https://lore.kernel.org/patchwork/cover/1284233/
Grygorii Strashko (2):
soc: ti: k3: ringacc: add am65x sr2.0 support
bindings: soc: ti: soc: ringacc: remove ti,dma-ring-reset-quirk
.../bindings/soc/ti/k3-ringacc.yaml | 6 ----
drivers/soc/ti/k3-ringacc.c | 33 +++++++++++++++++--
2 files changed, 30 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2020-09-09 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 19:43 Grygorii Strashko [this message]
2020-09-09 19:43 ` [RESEND PATCH next v2 1/2] " Grygorii Strashko
2020-09-09 19:43 ` [RESEND PATCH next v2 2/2] bindings: soc: ti: soc: ringacc: remove ti,dma-ring-reset-quirk Grygorii Strashko
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=20200909194338.21840-1-grygorii.strashko@ti.com \
--to=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@oracle.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®