From: Guru Das Srinagesh <quic_gurus@quicinc.com>
To: Robert Marko <robimarko@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Devicetree List <devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: firmware: qcom-scm: convert to dtschema
Date: Fri, 24 Jun 2022 18:57:14 -0700 [thread overview]
Message-ID: <20220625015714.GA6675@quicinc.com> (raw)
In-Reply-To: <CAOX2RU7yKuV4i_9YRs9fx2DTTvAndWFFw3cYtQ3qFk9m1zZJVg@mail.gmail.com>
On Jun 24 2022 10:50, Robert Marko wrote:
> On Fri, 24 Jun 2022 at 03:01, Guru Das Srinagesh <quic_gurus@quicinc.com> wrote:
> >
> > On Thu, Jun 23, 2022 at 08:25:42PM +0200, Robert Marko wrote:
> >
> > > +
> > > +description: |
> > ...
> > > +
> > > + '#reset-cells':
> > > + const: 1
> >
> > This isn't part of the original file - could you please explain why this is
> > being added?
>
> Yes, its not part of the original file, however I noticed that a lot of SCM
> nodes were adding #reset-cells, and upon looking at the SCM code its
> clear that it is being registered as a reset controller so #reset-cells are
> appropriate.
>
> However, since its not really being used via phandles #reset-cells did
> not really matter, hence why I did not add them to be required,
> this is something that DT guys can probably clarify.
Makes sense, ACK.
Thank you.
Guru Das.
next prev parent reply other threads:[~2022-06-25 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 18:25 [PATCH] dt-bindings: firmware: qcom-scm: convert to dtschema Robert Marko
2022-06-24 1:01 ` Guru Das Srinagesh
2022-06-24 8:50 ` Robert Marko
2022-06-25 1:57 ` Guru Das Srinagesh [this message]
2022-06-25 20:07 ` Krzysztof Kozlowski
2022-06-24 9:52 ` Krzysztof Kozlowski
2022-06-25 8:50 ` Robert Marko
2022-06-25 20:10 ` Krzysztof Kozlowski
2022-06-26 13:41 ` Robert Marko
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=20220625015714.GA6675@quicinc.com \
--to=quic_gurus@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
/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).