From: Conor.Dooley@microchip.com <Conor.Dooley@microchip.com>
To: opensbi@lists.infradead.org
Subject: [PATCH v10] platform: generic: andes/renesas: Add SBI EXT to check for enabling IOCP errata
Date: Tue, 11 Apr 2023 16:45:42 +0000 [thread overview]
Message-ID: <dc87f21a-4db4-5417-ecd9-43668e570708@microchip.com> (raw)
In-Reply-To: <20230411163633.11220-1-prabhakar.mahadev-lad.rj@bp.renesas.com>
On 11/04/2023 17:36, Lad Prabhakar wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> I/O Coherence Port (IOCP) provides an AXI interface for connecting
> external non-caching masters, such as DMA controllers. The accesses
> from IOCP are coherent with D-Caches and L2 Cache.
>
> IOCP is a specification option and is disabled on the Renesas RZ/Five
> SoC (which is based on Andes AX45MP core) due to this reason IP blocks
> using DMA will fail.
>
> As a workaround for SoCs with IOCP disabled CMO needs to be handled by
> software. Firstly OpenSBI configures the memory region as
> "Memory, Non-cacheable, Bufferable" and passes this region as a global
> shared dma pool as a DT node. With DMA_GLOBAL_POOL enabled all DMA
> allocations happen from this region and synchronization callbacks are
> implemented to synchronize when doing DMA transactions.
>
> SBI_EXT_ANDES_IOCP_SW_WORKAROUND checks if the IOCP errata should be
> applied to handle cache management.
I don't really have a nuanced opinion here, but I was happy a few
versions ago, so:
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
next prev parent reply other threads:[~2023-04-11 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 16:36 [PATCH v10] platform: generic: andes/renesas: Add SBI EXT to check for enabling IOCP errata Lad Prabhakar
2023-04-11 16:40 ` Anup Patel
2023-04-11 16:45 ` Conor.Dooley [this message]
2023-04-12 1:44 ` Yu-Chien Peter Lin
2023-04-14 12:11 ` Anup Patel
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=dc87f21a-4db4-5417-ecd9-43668e570708@microchip.com \
--to=conor.dooley@microchip.com \
--cc=opensbi@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.