linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Suman Anna <s-anna@ti.com>,
	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: Fri, 11 Sep 2020 21:55:07 -0700	[thread overview]
Message-ID: <a4bca7aa-b0b6-e033-6453-415600c638a7@oracle.com> (raw)
In-Reply-To: <39eeac89-b87b-e3ef-e061-20021e9bb0b9@oracle.com>

On 9/8/20 7:40 PM, santosh.shilimkar@oracle.com wrote:
> 
> 
> On 9/8/20 3:09 PM, Suman Anna wrote:
>> Hi Santosh,
>>
>> On 8/31/20 1:34 PM, santosh.shilimkar@oracle.com wrote:
>>> 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.
>>
>> PRUSS dt binding is acked now, so can you pick up the PRUSS v2 series 
>> for 5.10
>> merge window.
>>
> Yes, I saw ack from Rob. Will try to get to this over coming weekend.
> 
Applied. Should show up in linux-next

  reply	other threads:[~2020-09-12  4:55 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 ti,dma-ring-reset-quirk Grygorii Strashko
2020-08-31 18:34 ` [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support santosh.shilimkar
2020-09-02 14:08   ` 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 [this message]
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=a4bca7aa-b0b6-e033-6453-415600c638a7@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=s-anna@ti.com \
    --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).