linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: devicetree@vger.kernel.org,
	 linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	 Cristian Marussi <cristian.marussi@arm.com>,
	Kevin Hilman <khilman@baylibre.com>,
	 Neil Armstrong <narmstrong@baylibre.com>,
	Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH 1/8] dt-bindings: firmware: arm, scpi: Move arm, scpi-shmem to json schema
Date: Tue, 1 Jun 2021 08:37:57 -0500	[thread overview]
Message-ID: <CAL_Jsq+BGrU5Rb_fso3FK4T_1K+3zFbt_4m5RYAZwLNCGgYn-w@mail.gmail.com> (raw)
In-Reply-To: <20210531082002.spu73u7n35n53lqp@bogus>

On Mon, May 31, 2021 at 3:20 AM Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> On Mon, May 31, 2021 at 09:15:48AM +0100, Sudeep Holla wrote:
> > On Thu, May 27, 2021 at 03:25:54PM -0500, Rob Herring wrote:
> > > On Wed, May 26, 2021 at 07:28:00PM +0100, Sudeep Holla wrote:
> > > > Move the SRAM and shared memory binding for SCPI into the existing
> > > > Generic on-chip SRAM. We just need to update the compatible list and
> > > > there-by remove the whole old text format binding for the same.
> > > >
> > > > Cc: Rob Herring <robh+dt@kernel.org>
> > > > Cc: Kevin Hilman <khilman@baylibre.com>
> > > > Cc: Neil Armstrong <narmstrong@baylibre.com>
> > > > Cc: Jerome Brunet <jbrunet@baylibre.com>
> > > > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > > > ---
> > > >  .../devicetree/bindings/arm/arm,scpi.txt          | 15 ---------------
> > > >  Documentation/devicetree/bindings/sram/sram.yaml  |  1 +
> > > >  2 files changed, 1 insertion(+), 15 deletions(-)
> > > >
> > > > diff --git a/Documentation/devicetree/bindings/arm/arm,scpi.txt b/Documentation/devicetree/bindings/arm/arm,scpi.txt
> > > > index bcd6c3ec471e..bcb8b3d61e68 100644
> > > > --- a/Documentation/devicetree/bindings/arm/arm,scpi.txt
> > > > +++ b/Documentation/devicetree/bindings/arm/arm,scpi.txt
> > > > @@ -56,21 +56,6 @@ Sub-nodes
> > > >   node. It can be non linear and hence provide the mapping of identifiers
> > > >   into the clock-output-names array.
> > > >
> > > > -SRAM and Shared Memory for SCPI
> > > > --------------------------------
> > > > -
> > > > -A small area of SRAM is reserved for SCPI communication between application
> > > > -processors and SCP.
> > > > -
> > > > -The properties should follow the generic mmio-sram description found in [3]
> > > > -
> > > > -Each sub-node represents the reserved area for SCPI.
> > > > -
> > > > -Required sub-node properties:
> > > > -- reg : The base offset and size of the reserved area with the SRAM
> > > > -- compatible : should be "arm,scp-shmem" for Non-secure SRAM based
> > >
> > > > +            - arm,scpi-shmem
> > >
> > > Which is correct? There's not a single other occurrance in the kernel
> > > tree of either.
> > >
> >
> > Right I was thinking removing it but wasn't sure if any downstream DTS
> > have used this as it has been in the binding for a while now.
> >
>
> Sent it too early before I completed, we don't have explicit check for
> these compatible in the code. We just use phandles directly.

But which one is correct? "arm,scp-shmem" or "arm,scpi-shmem"

I can fix up when applying.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-01 13:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 18:27 [PATCH 0/8] dt-bindings: firmware: Convert SCPI and SCMI to json schema Sudeep Holla
2021-05-26 18:28 ` [PATCH 1/8] dt-bindings: firmware: arm, scpi: Move arm, scpi-shmem " Sudeep Holla
2021-05-27 20:25   ` Rob Herring
2021-05-31  8:15     ` Sudeep Holla
2021-05-31  8:20       ` Sudeep Holla
2021-06-01 13:37         ` Rob Herring [this message]
2021-06-01 13:53           ` Sudeep Holla
2021-05-26 18:28 ` [PATCH 2/8] dt-bindings: firmware: arm, scmi: Move arm, scmi-shmem " Sudeep Holla
2021-05-26 18:28 ` [PATCH 3/8] dt-bindings: firmware: juno, scpi: Move to sram.yaml " Sudeep Holla
2021-05-26 18:28 ` [PATCH 4/8] dt-bindings: firmware: amlogic, scpi: Move arm, scpi-shmem to " Sudeep Holla
2021-05-26 18:28 ` [PATCH 5/8] dt-bindings: firmware: arm,scpi: Convert " Sudeep Holla
2021-05-27 14:23   ` [PATCH 5/8] dt-bindings: firmware: arm, scpi: " Rob Herring
2021-05-27 16:17     ` [PATCH 5/8] dt-bindings: firmware: arm,scpi: " Sudeep Holla
2021-05-26 18:28 ` [PATCH 6/8] dt-bindings: mailbox : arm, mhu: Fix arm, scpi example used here Sudeep Holla
2021-05-27 14:23   ` Rob Herring
2021-05-27 16:25     ` Sudeep Holla
2021-05-27 20:07       ` Rob Herring
2021-05-31  8:17         ` Sudeep Holla
2021-05-26 18:28 ` [PATCH 7/8] dt-bindings: firmware: amlogic, scpi: Convert to json schema Sudeep Holla
2021-05-27 20:33   ` Rob Herring
2021-05-31  8:36     ` Sudeep Holla
2021-05-26 18:28 ` [PATCH 8/8] dt-bindings: firmware: arm,scmi: " Sudeep Holla
2021-05-26 18:35   ` Sudeep Holla
2021-05-27 20:15     ` [PATCH 8/8] dt-bindings: firmware: arm, scmi: " Rob Herring
2021-05-27  6:37   ` Etienne Carriere
2021-05-27 10:53     ` [PATCH 8/8] dt-bindings: firmware: arm,scmi: " Sudeep Holla
2021-05-27 10:33   ` Cristian Marussi
2021-05-27 10:49     ` Sudeep Holla

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=CAL_Jsq+BGrU5Rb_fso3FK4T_1K+3zFbt_4m5RYAZwLNCGgYn-w@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=narmstrong@baylibre.com \
    --cc=sudeep.holla@arm.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).