[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220419123331.14377-1-allen-kh.cheng@mediatek.com>
Date: Tue, 19 Apr 2022 20:33:29 +0800
From: Allen-KH Cheng <allen-kh.cheng@...iatek.com>
To: Ohad Ben-Cohen <ohad@...ery.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>
CC: 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>,
Allen-KH Cheng <allen-kh.cheng@...iatek.com>
Subject: [PATCH v3 0/2] remoteproc: mediatek: allow different SCP firmware names
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 +++++-
2 files changed, 12 insertions(+), 1 deletion(-)
--
2.18.0
Powered by blists - more mailing lists