linux-kernel - Re: [PATCH v7 3/6] reset: mchp: sparx5: Map cpu-syscon locally in case of LAN966x

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: <7c9f8ccc145bc9f62d3e5baaab24d1e4f6378436.camel@pengutronix.de>
Date: Wed, 09 Oct 2024 12:15:18 +0200
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Herve Codina <herve.codina@...tlin.com>, Geert Uytterhoeven
 <geert@...ux-m68k.org>, Andy Shevchenko <andy.shevchenko@...il.com>, Simon
 Horman <horms@...nel.org>, Lee Jones <lee@...nel.org>, Arnd Bergmann
 <arnd@...db.de>, Derek Kiernan <derek.kiernan@....com>, Dragan Cvetic
 <dragan.cvetic@....com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Bjorn Helgaas <bhelgaas@...gle.com>, Lars Povlsen
 <lars.povlsen@...rochip.com>, Steen Hegelund
 <Steen.Hegelund@...rochip.com>,  Daniel Machon
 <daniel.machon@...rochip.com>, UNGLinuxDriver@...rochip.com, Rob Herring
 <robh@...nel.org>,  Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Saravana Kannan <saravanak@...gle.com>
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
 <edumazet@...gle.com>,  Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
 <pabeni@...hat.com>, Horatiu Vultur <horatiu.vultur@...rochip.com>, Andrew
 Lunn <andrew@...n.ch>,  devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, netdev@...r.kernel.org, 
 linux-pci@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, Allan
 Nielsen <allan.nielsen@...rochip.com>, Luca Ceresoli
 <luca.ceresoli@...tlin.com>,  Thomas Petazzoni
 <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH v7 3/6] reset: mchp: sparx5: Map cpu-syscon locally in
 case of LAN966x

On Do, 2024-10-03 at 10:16 +0200, Herve Codina wrote:
> In the LAN966x PCI device use case, the syscon API cannot be used as
> it does not support device removal [1]. A syscon device is a core
> "system" device and not a device available in some addon boards and so,
> it is not supposed to be removed. The syscon API follows this assumption
> but this assumption is no longer valid in the LAN966x use case.
> 
> In order to avoid the use of the syscon API and so, support for removal,
> use a local mapping of the syscon device.
> 
> Link: https://lore.kernel.org/all/20240923100741.11277439@bootlin.com/ [1]
> Signed-off-by: Herve Codina <herve.codina@...tlin.com>

Reviewed-by: Philipp Zabel <p.zabel@...gutronix.de>

regards
Philipp