public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pranav Madhu" <pranav.madhu@arm.com>
To: Leif Lindholm <leif@nuviainc.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Ard Biesheuvel <Ard.Biesheuvel@arm.com>
Subject: Re: [edk2-platforms][PATCH v5 1/5] Silicon/ARM/N1SoC: Add platform library implementation
Date: Sun, 26 Jul 2020 16:21:25 +0000	[thread overview]
Message-ID: <AM6PR08MB4549636FB3E594AE815F81748A750@AM6PR08MB4549.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200724172910.GV1337@vanye>

Hi Leif,

> -----Original Message-----
> From: Leif Lindholm <leif@nuviainc.com>
> Sent: Friday, July 24, 2020 10:59 PM
> To: Pranav Madhu <Pranav.Madhu@arm.com>
> Cc: devel@edk2.groups.io; Ard Biesheuvel <Ard.Biesheuvel@arm.com>
> Subject: Re: [edk2-platforms][PATCH v5 1/5] Silicon/ARM/N1SoC: Add
> platform library implementation
>
> On Wed, Jul 22, 2020 at 20:55:20 +0530, Pranav Madhu wrote:
> > From: Deepak Pandey <deepak.pandey@arm.com>
> >
> > Add the initial Arm's Neoverse N1 System-on-Chip platform library
> > support. This includes the virtual memory map and helper functions for
> > platform initialization.
> >
> > Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
> > Cc: Leif Lindholm <leif@nuviainc.com>
> > Signed-off-by: Pranav Madhu <pranav.madhu@arm.com>
> > ---
> >  Silicon/ARM/NeoverseN1Soc/NeoverseN1Soc.dec                    |  27 +++++
> >  Silicon/ARM/NeoverseN1Soc/Library/PlatformLib/PlatformLib.inf  |  43
> +++++++
> >  Silicon/ARM/NeoverseN1Soc/Include/NeoverseN1Soc.h              |  66
> +++++++++++
> >  Silicon/ARM/NeoverseN1Soc/Library/PlatformLib/PlatformLib.c    |  67
> +++++++++++
> >  Silicon/ARM/NeoverseN1Soc/Library/PlatformLib/PlatformLibMem.c | 125
> > ++++++++++++++++++++
> > Silicon/ARM/NeoverseN1Soc/Library/PlatformLib/AArch64/Helper.S |  84
> > +++++++++++++
> >  6 files changed, 412 insertions(+)


<...>

> > +// Base address to a structure of type NEOVERSEN1SOC_PLAT_INFO
> which
> > +is // pre-populated by a earlier boot stage
> > +#define NEOVERSEN1SOC_PLAT_INFO_STRUCT_BASE
> (NEOVERSEN1SOC_NON_SECURE_SRAM_BASE + \
> > +                                                      0x00008000)
> > +
> > +/*
> > + * Platform information structure stored in non-secure SRAM. Platform
>
> The architectural terms as Secure an Non-secure. I asked for the latter. I will
> fix this up before pushing, but please pay attention to case for architectural
> terminology.
>
> Other than this, the patch is fine, so:
> Reviewed-by: Leif Lindholm <leif@nuviainc.com>

Thanks for fixing this up and your review of the patches. I'll take care of the case for architectural terminology henceforth.

Regards,
Pranav

<...>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2020-07-26 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 15:25 [edk2-platforms][PATCH v5 0/5] Add initial support for N1SDP board Pranav Madhu
2020-07-22 15:25 ` [edk2-platforms][PATCH v5 1/5] Silicon/ARM/N1SoC: Add platform library implementation Pranav Madhu
2020-07-24 17:29   ` Leif Lindholm
2020-07-26 16:21     ` Pranav Madhu [this message]
2020-07-22 15:25 ` [edk2-platforms][PATCH v5 2/5] Silicon/ARM/N1SoC: Implement Neoverse N1 SoC specific PciExpressLib Pranav Madhu
2020-07-24 18:37   ` Leif Lindholm
2020-07-22 15:25 ` [edk2-platforms][PATCH v5 3/5] Silicon/ARM/N1SoC: Implement the PciHostBridgeLib library Pranav Madhu
2020-07-22 15:25 ` [edk2-platforms][PATCH v5 4/5] Platform/ARM/N1SDP: Add initial N1SDP platform support Pranav Madhu
2020-07-22 15:25 ` [edk2-platforms][PATCH v5 5/5] Maintainers.txt: Add Silicon/ARM directory Pranav Madhu
2020-07-22 18:21 ` [edk2-devel] [edk2-platforms][PATCH v5 0/5] Add initial support for N1SDP board Thomas Abraham
2020-07-24 18:43 ` Leif Lindholm

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=AM6PR08MB4549636FB3E594AE815F81748A750@AM6PR08MB4549.eurprd08.prod.outlook.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