From: Rob Herring <robh@kernel.org>
Cc: Pi-Hsun Shih <pihsun@chromium.org>,
Nicolas Boichat <drinkcat@chromium.org>,
Erin Lo <erin.lo@mediatek.com>, Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
"open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM"
<linux-remoteproc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v3 1/5] dt-bindings: Add a binding for Mediatek SCP
Date: Mon, 21 Jan 2019 09:30:17 -0600 [thread overview]
Message-ID: <20190121153017.GA4608@bogus> (raw)
In-Reply-To: <20190121071833.43443-2-pihsun@chromium.org>
On Mon, 21 Jan 2019 15:18:29 +0800, Pi-Hsun Shih wrote:
> From: Erin Lo <erin.lo@mediatek.com>
>
> Add a DT binding documentation of SCP for the
> MT8183 SoC from Mediatek.
>
> Signed-off-by: Erin Lo <erin.lo@mediatek.com>
> ---
> Changes from v2:
> - No change. I realized that for this patch series, there's no need to
> add anything under the mt8183-scp node (neither the mt8183-rpmsg or
> the cros-ec-rpmsg) for them to work, since mt8183-rpmsg is added
> directly as a rproc_subdev by code, and cros-ec-rpmsg is dynamically
> created by SCP name service.
>
> Changes from v1:
> - No change.
> ---
> .../devicetree/bindings/remoteproc/mtk,scp.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/remoteproc/mtk,scp.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2019-01-21 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190121071833.43443-1-pihsun@chromium.org>
2019-01-21 7:18 ` [RFC v3 1/5] dt-bindings: Add a binding for Mediatek SCP Pi-Hsun Shih
2019-01-21 15:30 ` Rob Herring [this message]
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=20190121153017.GA4608@bogus \
--to=robh@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=erin.lo@mediatek.com \
--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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=ohad@wizery.com \
--cc=pihsun@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).