Messages in this thread | | | Subject | Re: [PATCH next v2 0/3] soc: ti: k3: ringacc: add am65x sr2.0 support | From | santosh.shilimkar@oracle ... | Date | Wed, 9 Sep 2020 09:52:55 -0700 |
| |
On 9/2/20 7:08 AM, Nishanth Menon wrote: > On 11:34-20200831, 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. > > > Santosh, in this series, may i suggest that the dtsi changes[1] be hosted > on my tree? else we are going to create a mix of rc1 and rc3 branches > which is going to be irritating, to say the least. > > I will pick [1] the day after I see the patches 1 and 2 in linux-next tag. > Sure !!
| |