public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: Yu-Chien Peter Lin <peter.lin@sifive.com>
Cc: <zong.li@sifive.com>, <greentime.hu@sifive.com>,
	<trini@konsulko.com>, <sjg@chromium.org>, <xypron.glpk@gmx.de>,
	<jiaxun.yang@flygoat.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH] Kconfig: Add a default cache line size for RISC-V
Date: Thu, 16 Jan 2025 11:21:23 +0800	[thread overview]
Message-ID: <Z4h7IsrhZWIg99pH@swlinux02> (raw)
In-Reply-To: <20250110085308.20760-1-peter.lin@sifive.com>

On Fri, Jan 10, 2025 at 04:53:08PM +0800, Yu-Chien Peter Lin wrote:
> [EXTERNAL MAIL]
> 
> Some RISC-V platforms do not define the d-cache line size
> through SYS_CACHE_SHIFT_n. Set a default value of 64 bytes
> for such cases.
> 
> Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> ---
> This patch resolves compilation errors that occurs when
> the TEE driver is enabled:
> 
>   drivers/tee/tee-uclass.c:247:41: error: 'CONFIG_SYS_CACHELINE_SIZE' undeclared (first use in this function); did you mean 'CONFIG_SYS_CBSIZE'?
>     247 |                                         CONFIG_SYS_CACHELINE_SIZE);
>         |                                         ^~~~~~~~~~~~~~~~~~~~~~~~~
>   drivers/tee/optee/core.c: In function 'flush_shm_dcache':
>   drivers/tee/optee/core.c:505:50: error: 'CONFIG_SYS_CACHELINE_SIZE' undeclared (first use in this function); did you mean 'CONFIG_SYS_CBSIZE'?
>     505 |         flush_dcache_range(rounddown((ulong)arg, CONFIG_SYS_CACHELINE_SIZE),
>         |                                                  ^~~~~~~~~~~~~~~~~~~~~~~~~
> ---
>  arch/Kconfig | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>

      parent reply	other threads:[~2025-01-16  3:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  8:53 [PATCH] Kconfig: Add a default cache line size for RISC-V Yu-Chien Peter Lin
2025-01-10 11:55 ` Heinrich Schuchardt
2025-01-16  3:21 ` Leo Liang [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=Z4h7IsrhZWIg99pH@swlinux02 \
    --to=ycliang@andestech.com \
    --cc=greentime.hu@sifive.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=peter.lin@sifive.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    --cc=zong.li@sifive.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