[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220426165708.GB2007637@p14s>
Date: Tue, 26 Apr 2022 10:57:08 -0600
From: Mathieu Poirier <mathieu.poirier@...aro.org>
To: Allen-KH Cheng <allen-kh.cheng@...iatek.com>
Cc: Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Hsin-Yi Wang <hsinyi@...omium.org>,
Project_Global_Chrome_Upstream_Group@...iatek.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-remoteproc@...r.kernel.org
Subject: Re: [PATCH v3 0/2] remoteproc: mediatek: allow different SCP
firmware names
On Tue, Apr 19, 2022 at 08:33:29PM +0800, Allen-KH Cheng wrote:
> The SCP needs firmware which differs between platforms and SoCs. Add a new
> property "firmware-name" to allow the DT to specify the platform/board specific
> path to this firmware file.
>
> The firmware-name property is optional and the code falls back to the
> old filename if the property isn't present.
>
> Base on remoteproc/linux.git, rproc-next (58b7c856519f)
>
> changes since v2:$
> - use rproc_of_parse_firmware instead of of_property_read_string
> changes since v1:
> - fix a misspelled word in commit title
>
> Allen-KH Cheng (2):
> dt-bindings: remoteproc: mediatek: add firmware-name property
> remoteproc: mediatek: allow reading firmware-name from DT
>
> Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml | 7 +++++++
> drivers/remoteproc/mtk_scp.c | 6 +++++-
I have applied this set.
Thanks,
Mathieu
> 2 files changed, 12 insertions(+), 1 deletion(-)
>
> --
> 2.18.0
>
Powered by blists - more mailing lists