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] [day] [month] [year] [list]
Message-ID: <a2eae87efe46ebf397bcec3580eb9bc152b80846.camel@collabora.com>
Date: Mon, 13 Oct 2025 15:41:49 +0200
From: Sjoerd Simons <sjoerd@...labora.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, 
	linux-mediatek@...ts.infradead.org
Cc: robh@...nel.org, conor+dt@...nel.org, mbrugger@...e.com, 
	y.oudjana@...tonmail.com, Nícolas "F. R. A. Prado"	
 <nfraprado@...labora.com>, linux-pm@...r.kernel.org,
 ulf.hansson@...aro.org, 	linux-kernel@...r.kernel.org,
 devicetree@...r.kernel.org, 	mandyjh.liu@...iatek.com,
 lihongbo22@...wei.com, wenst@...omium.org, 	matthias.bgg@...il.com,
 krzk+dt@...nel.org, kernel@...labora.com, 
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 04/10] pmdomain: mediatek: Refactor bus protection
 regmaps retrieval

Hey,

On Tue, 2025-08-05 at 09:47 +0200, AngeloGioacchino Del Regno wrote:
> In preparation to add support for new generation SoCs like MT8196,
> MT6991 and other variants, which require to set bus protection on
> different busses than the ones found on legacy chips, and to also
> simplify and reduce memory footprint of this driver, refactor the
> mechanism to retrieve and use the bus protection regmaps.
> 
> This is done by removing the three pointers to struct regmap from
> struct scpsys_domain (allocated for each power domain) and moving
> them to the main struct scpsys (allocated per driver instance) as
> an array of pointers to regmap named **bus_prot.

Trying to boot v6.18.0-rc1 on a Genio 700 EVK using the arm64 defconfig,
ends up hanging at boot (seemingly when probing MTU3 and/or mmc, but that 
might be a red herring). 

Either reverting this patch *or* having CONFIG_MTK_MMSYS builtin rather
then a module seems to solve that. 

-- 
Sjoerd Simons <sjoerd@...labora.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ