public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Achin Gupta <achin.gupta@arm.com>
Subject: Re: [PATCH v2 1/3] ArmPkg: Add PCDs needed for MM communication driver.
Date: Mon, 13 Nov 2017 05:00:14 -0600	[thread overview]
Message-ID: <1510570814.2604.8.camel@arm.com> (raw)
In-Reply-To: <CAKv+Gu9Zf8A3YqkrVdeuT=st8AeXJmroWZUHE4Vah8=yNOMX7g@mail.gmail.com>

On Mon, 2017-11-13 at 10:17 +0000, Ard Biesheuvel wrote:
> On 25 October 2017 at 17:32, Supreeth Venkatesh
> <supreeth.venkatesh@arm.com> wrote:
> > 
> > This patch defines PCDs to describe the base address and size of
> > communication buffer between normal world (uefi) and standalone MM
> > environment in the secure world.
> > 
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Achin Gupta <achin.gupta@arm.com>
> > Signed-off-by: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
> > ---
> >  ArmPkg/ArmPkg.dec | 3 +++
> >  1 file changed, 3 insertions(+)
> > 
> > diff --git a/ArmPkg/ArmPkg.dec b/ArmPkg/ArmPkg.dec
> > index f99054a7de..d871ecc654 100644
> > --- a/ArmPkg/ArmPkg.dec
> > +++ b/ArmPkg/ArmPkg.dec
> > @@ -229,6 +229,9 @@
> >    gArmTokenSpaceGuid.PcdSystemMemoryBase|0|UINT64|0x00000029
> >    gArmTokenSpaceGuid.PcdSystemMemorySize|0|UINT64|0x0000002A
> > 
> > +  gArmTokenSpaceGuid.PcdMmBufferBase|0|UINT64|0x00000045
> > +  gArmTokenSpaceGuid.PcdMmBufferSize|0|UINT64|0x00000046
> > +
> Do we need to hardcode this? Is there no way for the non-secure side
> to retrieve this information via SMC calls etc?
> 
This is not in the Specification yet. I am trying to get this added to
specification. Hence, for the time being, we are still using PCDs.

> > 
> >  [PcdsFixedAtBuild.common, PcdsDynamic.common]
> >    #
> >    # ARM Architectural Timer
> > --
> > 2.14.1
> > 


  reply	other threads:[~2017-11-13 10:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 16:32 [PATCH v2 0/3] *** EFI_MM_COMMUNICATION_PROTOCOL *** Supreeth Venkatesh
2017-10-25 16:32 ` [PATCH v2 1/3] ArmPkg: Add PCDs needed for MM communication driver Supreeth Venkatesh
2017-11-13 10:17   ` Ard Biesheuvel
2017-11-13 11:00     ` Supreeth Venkatesh [this message]
2017-10-25 16:32 ` [PATCH v2 2/3] ArmPkg/Drivers: Add EFI_MM_COMMUNICATION_PROTOCOL DXE driver Supreeth Venkatesh
2017-10-26  5:05   ` Udit Kumar
2017-10-26 15:14     ` Supreeth Venkatesh
2017-10-26 10:13   ` Achin Gupta
2017-10-26 16:03     ` Supreeth Venkatesh
2017-11-13 10:30   ` Ard Biesheuvel
2017-11-13 11:40     ` Supreeth Venkatesh
2017-11-13 11:48       ` Ard Biesheuvel
2017-11-13 12:15         ` Supreeth Venkatesh
2017-11-13 12:19           ` Ard Biesheuvel
2017-11-13 12:42             ` Supreeth Venkatesh
2017-11-13 12:46               ` Ard Biesheuvel
2017-10-25 16:32 ` [PATCH v2 3/3] ArmPkg/Drivers: Add ArmMmCommunication Driver information file Supreeth Venkatesh

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-list 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=1510570814.2604.8.camel@arm.com \
    --to=devel@edk2.groups.io \
    /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