lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250707003700.7c69ec68@minigeek.lan>
Date: Mon, 7 Jul 2025 00:37:00 +0100
From: Andre Przywara <andre.przywara@....com>
To: Chen-Yu Tsai <wens@...nel.org>
Cc: Chen-Yu Tsai <wens@...e.org>, Jernej Skrabec <jernej@...nel.org>, Samuel
 Holland <samuel@...lland.org>, Ulf Hansson <ulf.hansson@...aro.org>, Rob
 Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor
 Dooley <conor+dt@...nel.org>, linux-sunxi@...ts.linux.dev,
 devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH 2/4] pmdomain: sunxi: sun20i-ppu: add A523 support

On Fri, 27 Jun 2025 23:29:16 +0800
Chen-Yu Tsai <wens@...nel.org> wrote:

> From: Chen-Yu Tsai <wens@...e.org>
> 
> A523 has a PPU like the one in the Allwinner D1 SoC.
> 
> Add a compatible entry and a list of power domain names for it.

The user manual does not describe this PPU, but the BSP code confirms
the order of the domains, so:

> Signed-off-by: Chen-Yu Tsai <wens@...e.org>

Reviewed-by: Andre Przywara <andre.przywara@....com>

One suggestion below, but only if you respin anyway:

> ---
>  drivers/pmdomain/sunxi/sun20i-ppu.c | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/drivers/pmdomain/sunxi/sun20i-ppu.c b/drivers/pmdomain/sunxi/sun20i-ppu.c
> index 9f002748d224..b65876a68cc1 100644
> --- a/drivers/pmdomain/sunxi/sun20i-ppu.c
> +++ b/drivers/pmdomain/sunxi/sun20i-ppu.c
> @@ -193,6 +193,19 @@ static const struct sun20i_ppu_desc sun8i_v853_ppu_desc = {
>  	.num_domains	= ARRAY_SIZE(sun8i_v853_ppu_pd_names),
>  };
>  
> +static const char *const sun55i_a523_ppu_pd_names[] = {
> +	"DSP",

I wonder if we should enforce the relation between the DT binding
symbols and the names here, like:

	[PD_DSP] = "DSP",
	[PD_NPU] = "NPU",
	...

Cheers,
Andre


> +	"NPU",
> +	"AUDIO",
> +	"SRAM",
> +	"RISCV",
> +};
> +
> +static const struct sun20i_ppu_desc sun55i_a523_ppu_desc = {
> +	.names		= sun55i_a523_ppu_pd_names,
> +	.num_domains	= ARRAY_SIZE(sun55i_a523_ppu_pd_names),
> +};
> +
>  static const struct of_device_id sun20i_ppu_of_match[] = {
>  	{
>  		.compatible	= "allwinner,sun20i-d1-ppu",
> @@ -202,6 +215,10 @@ static const struct of_device_id sun20i_ppu_of_match[] = {
>  		.compatible	= "allwinner,sun8i-v853-ppu",
>  		.data		= &sun8i_v853_ppu_desc,
>  	},
> +	{
> +		.compatible	= "allwinner,sun55i-a523-ppu",
> +		.data		= &sun55i_a523_ppu_desc,
> +	},
>  	{ }
>  };
>  MODULE_DEVICE_TABLE(of, sun20i_ppu_of_match);


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ