[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <339f0d83-a28a-41f2-99ce-3fde0b5ef95e@oss.qualcomm.com>
Date: Thu, 3 Jul 2025 15:38:21 -0700
From: Jeff Johnson <jeff.johnson@....qualcomm.com>
To: "Rob Herring (Arm)" <robh@...nel.org>, Jeff Johnson
<jjohnson@...nel.org>,
Felix Fietkau <nbd@....name>, Lorenzo Bianconi <lorenzo@...nel.org>,
Ryder Lee <ryder.lee@...iatek.com>,
Shayne Chen <shayne.chen@...iatek.com>,
Sean Wang <sean.wang@...iatek.com>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: linux-wireless@...r.kernel.org, ath10k@...ts.infradead.org,
linux-kernel@...r.kernel.org, ath11k@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH] wireless: Use of_reserved_mem_region_to_resource() for
"memory-region"
On 7/3/2025 11:35 AM, Rob Herring (Arm) wrote:
> Use the newly added of_reserved_mem_region_to_resource() function to
> handle "memory-region" properties.
>
> The error handling is a bit different for ath10k. "memory-region" is
> optional, so failed lookup is not an error. But then an error in
> of_address_to_resource() is treated as an error. However, that
> distinction is not really important. Either the region is available
> and usable or it is not. So now, it is just
> of_reserved_mem_region_to_resource() which is checked for an error.
>
> Signed-off-by: Rob Herring (Arm) <robh@...nel.org>
> ---
> drivers/net/wireless/ath/ath10k/snoc.c | 14 +++----------
> drivers/net/wireless/ath/ath11k/ahb.c | 17 +++------------
> drivers/net/wireless/ath/ath11k/qmi.c | 17 ++++-----------
> .../net/wireless/mediatek/mt76/mt7915/soc.c | 21 +++++++------------
> 4 files changed, 18 insertions(+), 51 deletions(-)
Can you split the patch into 'ath' and 'mediatek' since those drivers go
through different trees.
/jeff
Powered by blists - more mailing lists