[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4c9b512f-59d2-4d96-a899-5af4de2c823e@kernel.org>
Date: Thu, 30 Jan 2025 08:46:30 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Raj Kumar Bhagat <quic_rajkbhag@...cinc.com>, ath12k@...ts.infradead.org
Cc: linux-wireless@...r.kernel.org, Kalle Valo <kvalo@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Jeff Johnson <jjohnson@...nel.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 07/13] wifi: ath12k: add support for fixed QMI firmware
memory
On 30/01/2025 05:35, Raj Kumar Bhagat wrote:
> @@ -2646,6 +2663,136 @@ static int ath12k_qmi_alloc_target_mem_chunk(struct ath12k_base *ab)
> return ret;
> }
>
> +static int ath12k_qmi_assign_target_mem_chunk(struct ath12k_base *ab)
> +{
> + struct device_node *mem_node;
> + struct resource res, m3_res;
> + u32 bdf_start_addr;
> + int i, idx, ret;
> +
> + for (i = 0, idx = 0; i < ab->qmi.mem_seg_count; i++) {
> + switch (ab->qmi.target_mem[i].type) {
> + case HOST_DDR_REGION_TYPE:
> + mem_node = ath12k_core_get_reserved_mem_by_name(ab, "q6-region");
Why cannot you use existing API for reserved memory -
of_reserved_mem_lookup()?
Best regards,
Krzysztof
Powered by blists - more mailing lists