From: Anup Patel <anup.patel@oss.qualcomm.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <pjw@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ian Rogers <irogers@google.com>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Liang Kan <kan.liang@linux.intel.com>,
Mayuresh Chitale <mchitale@gmail.com>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atish.patra@linux.dev>,
Andrew Jones <andrew.jones@oss.qualcomm.com>,
Sunil V L <sunilvl@oss.qualcomm.com>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Anup Patel <anup.patel@oss.qualcomm.com>
Subject: [PATCH v3 08/12] riscv: Enable DMA_RESTRICTED_POOL in defconfig
Date: Wed, 25 Feb 2026 11:54:44 +0530 [thread overview]
Message-ID: <20260225062448.4027948-9-anup.patel@oss.qualcomm.com> (raw)
In-Reply-To: <20260225062448.4027948-1-anup.patel@oss.qualcomm.com>
The RISC-V ramsink trace component may have implementation specific
restrictions such that the component can only write trace data in
particular parts of DRAM.
Enable DMA_RESTRICTED_POOL in the defconfig so that dma_alloc_*()
and dma_free_*() APIs work for devices with DMA address restrictions.
Signed-off-by: Anup Patel <anup.patel@oss.qualcomm.com>
---
arch/riscv/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs/defconfig
index b7cee9775f8d..42a1391480c6 100644
--- a/arch/riscv/configs/defconfig
+++ b/arch/riscv/configs/defconfig
@@ -308,6 +308,7 @@ CONFIG_SECURITY_APPARMOR=y
CONFIG_DEFAULT_SECURITY_DAC=y
CONFIG_CRYPTO_USER_API_HASH=y
CONFIG_CRYPTO_DEV_VIRTIO=y
+CONFIG_DMA_RESTRICTED_POOL=y
CONFIG_PRINTK_TIME=y
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_FS=y
--
2.43.0
next prev parent reply other threads:[~2026-02-25 6:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 6:24 [PATCH v3 00/12] Linux RISC-V trace framework and drivers Anup Patel
2026-02-25 6:24 ` [PATCH v3 01/12] dt-bindings: Add RISC-V trace component bindings Anup Patel
2026-02-25 6:24 ` [PATCH v3 02/12] rvtrace: Initial implementation of driver framework Anup Patel
2026-02-25 6:24 ` [PATCH v3 03/12] rvtrace: Add functions to create/destroy a trace component path Anup Patel
2026-02-25 6:24 ` [PATCH v3 04/12] rvtrace: Add functions to start/stop tracing on a " Anup Patel
2026-02-25 6:24 ` [PATCH v3 05/12] rvtrace: Add trace encoder driver Anup Patel
2026-02-25 6:24 ` [PATCH v3 06/12] rvtrace: Add function to copy into perf AUX buffer Anup Patel
2026-02-25 6:24 ` [PATCH v3 07/12] rvtrace: Add trace ramsink driver Anup Patel
2026-04-16 10:14 ` Eric Lin
2026-04-21 11:30 ` Mayuresh Chitale
2026-04-27 12:25 ` Mayuresh Chitale
2026-02-25 6:24 ` Anup Patel [this message]
2026-02-25 6:24 ` [PATCH v3 09/12] rvtrace: Add perf driver for tracing using perf tool Anup Patel
2026-02-25 6:24 ` [PATCH v3 10/12] perf tools: Add RISC-V trace PMU record capabilities Anup Patel
2026-02-25 6:24 ` [PATCH v3 11/12] perf tools: Initial support for RISC-V trace decoder Anup Patel
2026-02-25 6:24 ` [PATCH v3 12/12] MAINTAINERS: Add entry for RISC-V trace framework 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=20260225062448.4027948-9-anup.patel@oss.qualcomm.com \
--to=anup.patel@oss.qualcomm.com \
--cc=adrian.hunter@intel.com \
--cc=alex@ghiti.fr \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrew.jones@oss.qualcomm.com \
--cc=anup@brainfault.org \
--cc=atish.patra@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchitale@gmail.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=sunilvl@oss.qualcomm.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