From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Hsin-Yi Wang <hsinyi@chromium.org>,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] remoteproc: mediatek: allow reading firmware-name from DT
Date: Thu, 21 Apr 2022 12:12:03 +0200 [thread overview]
Message-ID: <2703f3de-1ee9-36ca-4866-89398c501244@collabora.com> (raw)
In-Reply-To: <20220419123331.14377-3-allen-kh.cheng@mediatek.com>
Il 19/04/22 14:33, Allen-KH Cheng ha scritto:
> The SCP firmware blob differs between platforms and SoCs. We add
> support in the SCP driver for reading the path of firmware file from
> DT in order to allow these files to live in a generic file system
> (or linux-firmware).
>
> The firmware-name property is optional and the code falls back to the
> old filename if the property isn't present.
>
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> Reviewed-by: Rex-BC Chen <rex-bc.chen@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
WARNING: multiple messages have this Message-ID (diff)
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Hsin-Yi Wang <hsinyi@chromium.org>,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] remoteproc: mediatek: allow reading firmware-name from DT
Date: Thu, 21 Apr 2022 12:12:03 +0200 [thread overview]
Message-ID: <2703f3de-1ee9-36ca-4866-89398c501244@collabora.com> (raw)
In-Reply-To: <20220419123331.14377-3-allen-kh.cheng@mediatek.com>
Il 19/04/22 14:33, Allen-KH Cheng ha scritto:
> The SCP firmware blob differs between platforms and SoCs. We add
> support in the SCP driver for reading the path of firmware file from
> DT in order to allow these files to live in a generic file system
> (or linux-firmware).
>
> The firmware-name property is optional and the code falls back to the
> old filename if the property isn't present.
>
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> Reviewed-by: Rex-BC Chen <rex-bc.chen@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Hsin-Yi Wang <hsinyi@chromium.org>,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] remoteproc: mediatek: allow reading firmware-name from DT
Date: Thu, 21 Apr 2022 12:12:03 +0200 [thread overview]
Message-ID: <2703f3de-1ee9-36ca-4866-89398c501244@collabora.com> (raw)
In-Reply-To: <20220419123331.14377-3-allen-kh.cheng@mediatek.com>
Il 19/04/22 14:33, Allen-KH Cheng ha scritto:
> The SCP firmware blob differs between platforms and SoCs. We add
> support in the SCP driver for reading the path of firmware file from
> DT in order to allow these files to live in a generic file system
> (or linux-firmware).
>
> The firmware-name property is optional and the code falls back to the
> old filename if the property isn't present.
>
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> Reviewed-by: Rex-BC Chen <rex-bc.chen@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-21 10:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 12:33 [PATCH v3 0/2] remoteproc: mediatek: allow different SCP firmware names Allen-KH Cheng
2022-04-19 12:33 ` Allen-KH Cheng
2022-04-19 12:33 ` Allen-KH Cheng
2022-04-19 12:33 ` [PATCH v3 1/2] dt-bindings: remoteproc: mediatek: add firmware-name property Allen-KH Cheng
2022-04-19 12:33 ` Allen-KH Cheng
2022-04-19 12:33 ` Allen-KH Cheng
2022-04-26 0:28 ` Rob Herring
2022-04-26 0:28 ` Rob Herring
2022-04-26 0:28 ` Rob Herring
2022-04-19 12:33 ` [PATCH v3 2/2] remoteproc: mediatek: allow reading firmware-name from DT Allen-KH Cheng
2022-04-19 12:33 ` Allen-KH Cheng
2022-04-19 12:33 ` Allen-KH Cheng
2022-04-21 6:23 ` Rex-BC Chen
2022-04-21 6:23 ` Rex-BC Chen
2022-04-21 6:23 ` Rex-BC Chen
2022-04-21 10:12 ` AngeloGioacchino Del Regno [this message]
2022-04-21 10:12 ` AngeloGioacchino Del Regno
2022-04-21 10:12 ` AngeloGioacchino Del Regno
2022-04-21 16:21 ` [PATCH v3 0/2] remoteproc: mediatek: allow different SCP firmware names Mathieu Poirier
2022-04-21 16:21 ` Mathieu Poirier
2022-04-21 16:21 ` Mathieu Poirier
2022-04-26 16:57 ` Mathieu Poirier
2022-04-26 16:57 ` Mathieu Poirier
2022-04-26 16:57 ` Mathieu Poirier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2703f3de-1ee9-36ca-4866-89398c501244@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=matthias.bgg@gmail.com \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.