From: <pillair@codeaurora.org>
To: "'Stephen Boyd'" <swboyd@chromium.org>, <agross@kernel.org>,
<bjorn.andersson@linaro.org>, <mathieu.poirier@linaro.org>,
<ohad@wizery.com>, <p.zabel@pengutronix.de>, <robh+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <sibis@codeaurora.org>,
<mpubbise@codeaurora.org>, <kuabhs@chromium.org>
Subject: RE: [PATCH v7 2/3] dt-bindings: remoteproc: qcom: Add SC7280 WPSS support
Date: Tue, 2 Nov 2021 19:15:09 +0530 [thread overview]
Message-ID: <001f01d7cfef$dee34a50$9ca9def0$@codeaurora.org> (raw)
In-Reply-To: <CAE-0n5155J4vvvFES9V5=v+nX3BhZsBgZxkB=uLQOPij=-sf-Q@mail.gmail.com>
> -----Original Message-----
> From: Stephen Boyd <swboyd@chromium.org>
> Sent: Saturday, October 30, 2021 12:34 AM
> To: agross@kernel.org; bjorn.andersson@linaro.org;
> mathieu.poirier@linaro.org; ohad@wizery.com; p.zabel@pengutronix.de;
> pillair@codeaurora.org; robh+dt@kernel.org
> Cc: linux-arm-msm@vger.kernel.org; linux-remoteproc@vger.kernel.org;
> devicetree@vger.kernel.org; linux-kernel@vger.kernel.org;
> sibis@codeaurora.org; mpubbise@codeaurora.org; kuabhs@chromium.org
> Subject: RE: [PATCH v7 2/3] dt-bindings: remoteproc: qcom: Add SC7280
> WPSS support
>
> Quoting pillair@codeaurora.org (2021-10-29 03:46:03)
> >
> > > > +
> > > > + glink-edge {
> > > > + interrupts-extended = <&ipcc IPCC_CLIENT_WPSS
> > > > + IPCC_MPROC_SIGNAL_GLINK_QMP
> > > > + IRQ_TYPE_EDGE_RISING>;
> > > > + mboxes = <&ipcc IPCC_CLIENT_WPSS
> > > > + IPCC_MPROC_SIGNAL_GLINK_QMP>;
> > > > +
> > > > + label = "wpss";
> > > > + qcom,remote-pid = <13>;
> > >
> > > There are a few properties here that don't seem to be required. Is
> > > that intentional?
> >
> > Hi Stephen,
> > All the properties in the example are listed as required (except for status,
> which will be removed in the subsequent patchset).
> > Do you mean the glink-edge node properties ?
>
> Yes I mean all the properties in the glink-edge node. Are they required?
> If so then we need to list them in the schema.
Hi Stephen,
I have sent v8 with glink-edge properties also included in the dt-bindings.
Thanks,
Rakesh Pillai.
next prev parent reply other threads:[~2021-11-02 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 8:13 [PATCH v7 0/3] Add support for sc7280 WPSS PIL loading Rakesh Pillai
2021-10-28 8:13 ` [PATCH v7 1/3] dt-bindings: remoteproc: qcom: adsp: Convert binding to YAML Rakesh Pillai
2021-10-28 22:05 ` Stephen Boyd
2021-10-28 8:13 ` [PATCH v7 2/3] dt-bindings: remoteproc: qcom: Add SC7280 WPSS support Rakesh Pillai
2021-10-28 22:08 ` Stephen Boyd
2021-10-29 10:46 ` pillair
2021-10-29 19:04 ` Stephen Boyd
2021-11-02 13:45 ` pillair [this message]
2021-11-02 14:26 ` Rob Herring
2021-10-28 8:13 ` [PATCH v7 3/3] remoteproc: qcom: q6v5_wpss: Add support for sc7280 WPSS Rakesh Pillai
2021-10-28 22:12 ` Stephen Boyd
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='001f01d7cfef$dee34a50$9ca9def0$@codeaurora.org' \
--to=pillair@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kuabhs@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mpubbise@codeaurora.org \
--cc=ohad@wizery.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=sibis@codeaurora.org \
--cc=swboyd@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 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.