public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>,
	u-boot@lists.denx.de
Cc: git@xilinx.com
Subject: Re: [PATCH 0/2] Fix the tcminit command
Date: Mon, 12 Jun 2023 08:35:09 +0200	[thread overview]
Message-ID: <89fa0abf-1bfe-5653-5b14-059451958c0e@amd.com> (raw)
In-Reply-To: <20230608032152.980-1-venkatesh.abbarapu@amd.com>



On 6/8/23 05:21, Venkatesh Yadav Abbarapu wrote:
> Fix the tcminit mode param and cpu release lockstep
> functionality.
> 
> 
> Venkatesh Yadav Abbarapu (2):
>    arm64: zynqmp: Fix tcminit mode param
>    arm64: zynqmp: Fix lockstep mode cpu release functionality
> 
>   arch/arm/mach-zynqmp/mp.c  | 4 ++++
>   board/xilinx/zynqmp/cmds.c | 5 +++++
>   2 files changed, 9 insertions(+)
> 

Applied but can you please also update command documentation to use
lockstep instead of lock?


  439         "zynqmp tcminit mode - Initialize the TCM with zeros. TCM needs to 
be\n"
  440         "                      initialized before accessing to avoid ECC\n"
  441         "                      errors. mode specifies in which mode TCM has\n"
  442         "                      to be initialized. Supported modes will be\n"
  443         "                      lock(0)/split(1)\n"

Thanks,
Michal

      parent reply	other threads:[~2023-06-12  6:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08  3:21 [PATCH 0/2] Fix the tcminit command Venkatesh Yadav Abbarapu
2023-06-08  3:21 ` [PATCH 1/2] arm64: zynqmp: Fix tcminit mode param Venkatesh Yadav Abbarapu
2023-06-08  3:21 ` [PATCH 2/2] arm64: zynqmp: Fix lockstep mode cpu release functionality Venkatesh Yadav Abbarapu
2023-06-12  6:35 ` Michal Simek [this message]

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=89fa0abf-1bfe-5653-5b14-059451958c0e@amd.com \
    --to=michal.simek@amd.com \
    --cc=git@xilinx.com \
    --cc=u-boot@lists.denx.de \
    --cc=venkatesh.abbarapu@amd.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