All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [RFC PATCH 1/3] dt-bindings: Add ARM PSA FF binding for non-secure VM partitions
Date: Wed, 10 Jun 2020 09:32:37 +0100	[thread overview]
Message-ID: <20200610083237.GA4867@bogus> (raw)
In-Reply-To: <20200609223551.GA1620273@bogus>

On Tue, Jun 09, 2020 at 04:35:51PM -0600, Rob Herring wrote:
> On Mon, Jun 01, 2020 at 10:45:10AM +0100, Sudeep Holla wrote:
> > Add devicetree bindings for a Arm PSA FF-A compliant non-secure partition
> > at virtual interface(VMs).
> >
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > ---
> >  .../devicetree/bindings/arm/arm,psa-ffa.txt   | 47 +++++++++++++++++++
> >  1 file changed, 47 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/arm/arm,psa-ffa.txt
>
> I'm hoping this goes away if the firmware is discoverable, but if not DT
> bindings are DT schema now.
>

Yes, consider it gone. I introduced it to couple of reasons both of which
are now irrelevant. We may revisit this if we need it for Rx/Tx buffer
information. The KVM host may need the binding, this was for the guests/
partitions as Will has already mentioned.

--
Regards,
Sudeep

WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
	linux-kernel@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 1/3] dt-bindings: Add ARM PSA FF binding for non-secure VM partitions
Date: Wed, 10 Jun 2020 09:32:37 +0100	[thread overview]
Message-ID: <20200610083237.GA4867@bogus> (raw)
In-Reply-To: <20200609223551.GA1620273@bogus>

On Tue, Jun 09, 2020 at 04:35:51PM -0600, Rob Herring wrote:
> On Mon, Jun 01, 2020 at 10:45:10AM +0100, Sudeep Holla wrote:
> > Add devicetree bindings for a Arm PSA FF-A compliant non-secure partition
> > at virtual interface(VMs).
> >
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > ---
> >  .../devicetree/bindings/arm/arm,psa-ffa.txt   | 47 +++++++++++++++++++
> >  1 file changed, 47 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/arm/arm,psa-ffa.txt
>
> I'm hoping this goes away if the firmware is discoverable, but if not DT
> bindings are DT schema now.
>

Yes, consider it gone. I introduced it to couple of reasons both of which
are now irrelevant. We may revisit this if we need it for Rx/Tx buffer
information. The KVM host may need the binding, this was for the guests/
partitions as Will has already mentioned.

--
Regards,
Sudeep

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

  parent reply	other threads:[~2020-06-10  8:32 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01  9:45 [RFC PATCH 0/3] firmware: Add support for PSA FF-A interface Sudeep Holla
2020-06-01  9:45 ` Sudeep Holla
2020-06-01  9:45 ` [RFC PATCH 1/3] dt-bindings: Add ARM PSA FF binding for non-secure VM partitions Sudeep Holla
2020-06-01  9:45   ` Sudeep Holla
2020-06-09 22:35   ` Rob Herring
2020-06-09 22:35     ` Rob Herring
2020-06-10  7:43     ` Will Deacon
2020-06-10  7:43       ` Will Deacon
2020-06-10 13:56       ` Rob Herring
2020-06-10 13:56         ` Rob Herring
2020-06-11 15:46       ` Achin Gupta
2020-06-11 15:46         ` Achin Gupta
2020-06-11 17:12         ` Will Deacon
2020-06-11 17:12           ` Will Deacon
2020-06-15  9:16           ` Achin Gupta
2020-06-15  9:16             ` Achin Gupta
2020-06-15  9:51             ` Will Deacon
2020-06-15  9:51               ` Will Deacon
2020-06-15 11:42               ` Achin Gupta
2020-06-15 11:42                 ` Achin Gupta
2020-06-15 11:55                 ` Will Deacon
2020-06-15 11:55                   ` Will Deacon
2020-06-15 16:48                   ` Achin Gupta
2020-06-15 16:48                     ` Achin Gupta
2020-06-10  8:32     ` Sudeep Holla [this message]
2020-06-10  8:32       ` Sudeep Holla
2020-06-01  9:45 ` [RFC PATCH 2/3] firmware: Add support for PSA FF-A transport for " Sudeep Holla
2020-06-01  9:45   ` Sudeep Holla
2020-06-01 13:46   ` kbuild test robot
2020-06-02  7:11   ` kbuild test robot
2020-07-09 22:15   ` Arve Hjønnevåg
2020-07-09 22:15     ` Arve Hjønnevåg
2020-06-01  9:45 ` [RFC PATCH 3/3] firmware: Add example PSA FF-A non-secure VM partition Sudeep Holla
2020-06-01  9:45   ` Sudeep Holla
2020-06-01 14:22   ` kbuild test robot
2020-06-04 13:37 ` [RFC PATCH 0/3] firmware: Add support for PSA FF-A interface Will Deacon
2020-06-04 13:37   ` Will Deacon
2020-06-09 17:41   ` Sudeep Holla
2020-06-09 17:41     ` Sudeep Holla
2020-06-10  7:57     ` Will Deacon
2020-06-10  7:57       ` Will Deacon
2020-06-10  8:10       ` Sudeep Holla
2020-06-10  8:10         ` Sudeep Holla
2020-06-15 11:38     ` Jens Wiklander
2020-06-15 11:38       ` Jens Wiklander

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=20200610083237.GA4867@bogus \
    --to=sudeep.holla@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=will@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.