From: santosh.shilimkar@oracle.com
To: Grygorii Strashko <grygorii.strashko@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Tero Kristo <t-kristo@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>, Sekhar Nori <nsekhar@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support
Date: Mon, 31 Aug 2020 11:34:53 -0700 [thread overview]
Message-ID: <b9310d10-46c5-2c63-a921-88be23363d44@oracle.com> (raw)
In-Reply-To: <20200829184139.15547-1-grygorii.strashko@ti.com>
On 8/29/20 11:41 AM, Grygorii Strashko wrote:
> Hi Santosh,
>
> I've rebased on top of linux-next and identified merge conflict of patch 3
> with commit 6da45875fa17 ("arm64: dts: k3-am65: Update the RM resource types")
> in -next.
>
> ---
> 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
>
Thanks. Can you please followup DT acks for PRUSS series so that I can
apply PRUSS + $subject series.
> v1: https://urldefense.com/v3/__https://lore.kernel.org/patchwork/cover/1284233/__;!!GqivPVa7Brio!PCmZ-nZZ6YQak-0T43bPZYI0gHsYL9k6N7S2gZEFbIr8BRKtv2BK01VejQzlBPBBgcfvCQ$
>
> Grygorii Strashko (3):
> soc: ti: k3: ringacc: add am65x sr2.0 support
> bindings: soc: ti: soc: ringacc: remove ti,dma-ring-reset-quirk
> arm64: dts: ti: k3-am65: ringacc: drop ti,dma-ring-reset-quirk
>
> .../bindings/soc/ti/k3-ringacc.yaml | 6 ----
> arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 1 -
> arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 1 -
> drivers/soc/ti/k3-ringacc.c | 33 +++++++++++++++++--
> 4 files changed, 30 insertions(+), 11 deletions(-)
>
_______________________________________________
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:[~2020-08-31 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 18:41 [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 1/3] " Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 2/3] bindings: soc: ti: soc: ringacc: remove ti, dma-ring-reset-quirk Grygorii Strashko
2020-08-29 18:41 ` [PATCH next v2 3/3] arm64: dts: ti: k3-am65: ringacc: drop " Grygorii Strashko
2020-08-31 18:34 ` santosh.shilimkar [this message]
2020-09-02 14:08 ` [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support Nishanth Menon
2020-09-09 16:52 ` santosh.shilimkar
2020-09-12 4:54 ` santosh.shilimkar
2020-09-08 22:09 ` Suman Anna
2020-09-09 2:40 ` santosh.shilimkar
2020-09-12 4:55 ` santosh.shilimkar
2020-09-14 12:34 ` Nishanth Menon
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=b9310d10-46c5-2c63-a921-88be23363d44@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=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=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=vigneshr@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).