[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <168945033424.1736171.17829824538701917090.b4-ty@kernel.org>
Date: Sat, 15 Jul 2023 12:45:37 -0700
From: Bjorn Andersson <andersson@...nel.org>
To: Stephan Gerhold <stephan@...hold.net>
Cc: Andy Gross <agross@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Caleb Connolly <caleb.connolly@...aro.org>
Subject: Re: [PATCH v3] remoteproc: qcom: Use of_reserved_mem_lookup()
On Mon, 10 Jul 2023 22:34:52 +0200, Stephan Gerhold wrote:
> Reserved memory can be either looked up using the generic function
> of_address_to_resource() or using the special of_reserved_mem_lookup().
> The latter has the advantage that it ensures that the referenced memory
> region was really reserved and is not e.g. status = "disabled".
>
> of_reserved_mem also supports allocating reserved memory dynamically at
> boot time. This works only when using of_reserved_mem_lookup() since
> there won't be a fixed address in the device tree.
>
> [...]
Applied, thanks!
[1/1] remoteproc: qcom: Use of_reserved_mem_lookup()
commit: 0ee55c188a3c97309a6794077d5ef4ebd58f62cb
Best regards,
--
Bjorn Andersson <andersson@...nel.org>
Powered by blists - more mailing lists