From: Krzysztof Kozlowski <krzk@kernel.org>
To: Santhosh Kumar K <s-k6@ti.com>
Cc: robh@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Fix OSPI DMA corruption via FSS_FSAS driver
Date: Tue, 30 Jun 2026 09:13:04 +0200 [thread overview]
Message-ID: <20260630-advanced-passionate-fossa-6beec0@quoll> (raw)
In-Reply-To: <20260629072055.896322-1-s-k6@ti.com>
On Mon, Jun 29, 2026 at 12:50:53PM +0530, Santhosh Kumar K wrote:
> On TI K3 SoCs, DMA transfers from OSPI produce corrupted data when the
> source address is only 4-byte aligned (not 4K-aligned). The root cause
> is XIP read prefetch in the FSS_FSAS_GENREGS wrapper (SYSCONFIG.DISXIP,
> bit 7), which is enabled by default.
>
> This series adds a dedicated FSS_FSAS platform driver that disables XIP
> prefetch at probe, plus the respective DT binding.
>
> Testing:
> This series was tested on TI's
> AM62Ax SK with OSPI NAND flash and
> AM62Px SK with OSPI NOR flash:
>
> Test log: https://gist.github.com/santhosh21/3ac2a0273065e86315a9b442327c9599
> Repo: https://github.com/santhosh21/linux/commits/fsas
Three versions within one day that's way too much. And b4 diff does not
work:
b4 diff 20260629072055.896322-1-s-k6@ti.com
Looking up https://lore.kernel.org/all/20260629072055.896322-1-s-k6@ti.com/
Grabbing thread from lore.kernel.org/all/20260629072055.896322-1-s-k6@ti.com/t.mbox.gz
Checking for older revisions
Grabbing search results from lore.kernel.org
Added from v1: 6 patches
---
Analyzing 14 messages in the thread
WARNING: duplicate messages found at index 2
Subject 1: memory: ti-k3-fsas: Add TI FSS_FSAS driver
Subject 2: memory: ti-k3-fsas: Add TI FSS_FSAS driver
2 is not a reply... assume additional patch
WARNING: duplicate messages found at index 1
Subject 1: dt-bindings: memory: Add TI FSS_FSAS binding
Subject 2: dt-bindings: memory: Add TI FSS_FSAS binding
2 is not a reply... assume additional patch
Preparing fake-am for v1: dt-bindings: memory: Add TI FSS_FSAS binding
ERROR: v1 series incomplete; unable to create a fake-am range
If you want to make it difficult for maintainer to review, your patches
will be moved to the end of the queue.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-06-30 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 7:20 Santhosh Kumar K
2026-06-29 7:20 ` [PATCH v2 1/2] dt-bindings: memory: Add TI FSS_FSAS binding Santhosh Kumar K
2026-07-02 16:33 ` Rob Herring (Arm)
2026-07-08 11:07 ` Krzysztof Kozlowski
2026-06-29 7:20 ` [PATCH v2 2/2] memory: ti-k3-fsas: Add TI FSS_FSAS driver Santhosh Kumar K
2026-07-08 11:09 ` Krzysztof Kozlowski
2026-06-30 7:13 ` Krzysztof Kozlowski [this message]
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=20260630-advanced-passionate-fossa-6beec0@quoll \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s-k6@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
all inboxes | Powered by JetHome®