public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: Romain Naour <romain.naour@smile.fr>,
	tony@atomide.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org
Cc: linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	stable@kernel.org, Romain Naour <romain.naour@skf.com>
Subject: Re: [PATCH] ARM: dts: dra7: Add bus_dma_limit for l4 cfg bus
Date: Fri, 15 Nov 2024 11:20:39 +0200	[thread overview]
Message-ID: <e4c45744-3e5d-4ded-a33e-0d9097aebcaa@kernel.org> (raw)
In-Reply-To: <20241114155759.1155567-1-romain.naour@smile.fr>



On 14/11/2024 17:57, Romain Naour wrote:
> From: Romain Naour <romain.naour@skf.com>
> 
> A bus_dma_limit was added for l3 bus by commit cfb5d65f2595
> ("ARM: dts: dra7: Add bus_dma_limit for L3 bus") to fix an issue
> observed only with SATA on DRA7-EVM with 4GB RAM and CONFIG_ARM_LPAE
> enabled.
> 
> Since kernel 5.13, the SATA issue can be reproduced again following
> the SATA node move from L3 bus to L4_cfg in commit 8af15365a368
> ("ARM: dts: Configure interconnect target module for dra7 sata").
> 
> Fix it by adding an empty dma-ranges property to l4_cfg and
> segment@100000 nodes (parent device tree node of SATA controller) to
> inherit the 2GB dma ranges limit from l3 bus node.
> 
> Note: A similar fix was applied for PCIe controller by commit
> 90d4d3f4ea45 ("ARM: dts: dra7: Fix bus_dma_limit for PCIe").
> 
> Fixes: 8af15365a368 ("ARM: dts: Configure interconnect target module for dra7 sata").
> Link: https://lore.kernel.org/linux-omap/c583e1bb-f56b-4489-8012-ce742e85f233@smile.fr/

Please add the stable tag here

Cc: <stable@vger.kernel.org> # 5.13

> Signed-off-by: Romain Naour <romain.naour@skf.com>
> ---

-- 
cheers,
-roger


  reply	other threads:[~2024-11-15  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 15:57 [PATCH] ARM: dts: dra7: Add bus_dma_limit for l4 cfg bus Romain Naour
2024-11-15  9:20 ` Roger Quadros [this message]
2024-11-15 10:28   ` Romain Naour

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=e4c45744-3e5d-4ded-a33e-0d9097aebcaa@kernel.org \
    --to=rogerq@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=romain.naour@skf.com \
    --cc=romain.naour@smile.fr \
    --cc=stable@kernel.org \
    --cc=tony@atomide.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