U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Kumar, Udit" <u-kumar1@ti.com>
To: Neha Malcom Francis <n-francis@ti.com>, <trini@konsulko.com>
Cc: <vaishnav.a@ti.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH] board: ti: j784s4: Update Resource Management configs
Date: Thu, 27 Feb 2025 13:40:56 +0530	[thread overview]
Message-ID: <a9a79115-2ef3-456c-8fa1-e80fbfc40bb0@ti.com> (raw)
In-Reply-To: <20250227064947.2475315-1-n-francis@ti.com>


On 2/27/2025 12:19 PM, Neha Malcom Francis wrote:
> From: Vaishnav Achath <vaishnav.a@ti.com>
>
> Update rm-cfg.yaml and tifs-rm-cfg.yaml to account for the
> latest changes added in the K3 Resource Partitioning Tool.

Please give the version of this tool instead of latest :)


>
> The change enables resource sharing between A72_2 and MAIN_0_R5_0
> for the BCDMA CSI RX and TX channels, J784S4 supports upto 12
> CSI cameras and 16 channels would not be enough for all such use
> cases for RTOS and Linux, thus sharing of resources in needed.

Please add in commit message, what you are doing to overcome with 
limitation.

Something like, increasing channels to 32 or so .

With above changes in commit message,

Reviewed-by: Udit Kumar <u-kumar1@ti.com>


>
> Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
> [n-francis@ti.com: rebased and sent on behalf]
> Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
> ---
>   board/ti/j784s4/rm-cfg.yaml      | 24 ++++++++++++------------
>   board/ti/j784s4/tifs-rm-cfg.yaml | 24 ++++++++++++------------
>   2 files changed, 24 insertions(+), 24 deletions(-)
>
> diff --git a/board/ti/j784s4/rm-cfg.yaml b/board/ti/j784s4/rm-cfg.yaml
> index a448bd2e1e0..6968d317522 100644
> --- a/board/ti/j784s4/rm-cfg.yaml
> +++ b/board/ti/j784s4/rm-cfg.yaml
> @@ -406,49 +406,49 @@ rm-cfg:
>               reserved: 0
> [..]

      reply	other threads:[~2025-02-27  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27  6:49 [PATCH] board: ti: j784s4: Update Resource Management configs Neha Malcom Francis
2025-02-27  8:10 ` Kumar, Udit [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=a9a79115-2ef3-456c-8fa1-e80fbfc40bb0@ti.com \
    --to=u-kumar1@ti.com \
    --cc=n-francis@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vaishnav.a@ti.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