| Message ID | 20200829184139.15547-1-grygorii.strashko@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | soc: ti: k3: ringacc: add am65x sr2.0 support | expand |
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(-) >
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. [1] https://lore.kernel.org/lkml/20200829184139.15547-4-grygorii.strashko@ti.com/
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. regards, Suman > >> 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
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. Regards, Santosh
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 !!
On 9/9/20 9:52 AM, santosh.shilimkar@oracle.com wrote: > 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: [..] >> >> >> 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 !! Applied. Should show up in linux-next
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
On Sat, 29 Aug 2020 21:41:36 +0300, Grygorii Strashko wrote: > 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. Hi Grygorii Strashko, I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/1] arm64: dts: ti: k3-am65: ringacc: drop ti, dma-ring-reset-quirk commit: 69fba6172b9f03ad1079c9c72f5cf0c623a18c6d All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. [1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
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 v1: https://lore.kernel.org/patchwork/cover/1284233/ 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(-)