From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from metis.whiteo.stw.pengutronix.de (metis.whiteo.stw.pengutronix.de [185.203.201.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 93CF318FC7E for ; Wed, 9 Oct 2024 10:15:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.203.201.7 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728468958; cv=none; b=snfZ+nL+AZMye1wiYiz23KhJYro6FnBsTWnfGsyWWnWEBbgiPcMUqCPFBBK1l4gfleMXbbNlz66Rxnvu4HmKuI0ja8kE+sAxEpI0nwlxHECBYFmB6thwTwKlRLxiiNZvjFolC+EmH0r9Y8br6fhR73+GJzPFxF8mW2+jGtI52Pc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1728468958; c=relaxed/simple; bh=yRYz0Zsqxya1VheS4IuNYc94S2kSLleMvc7LIeAdnm4=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=LCmhSUdJrXO4guVB92g9mzEO+AIaTb6+qPYWKiugIRdwiqBrtLGXcrK/Oc4XJw8SQMNfxkxgOmuJ9VYUJFyjuFlqXSmanj7bo1GSTiKiIj3YzBZb8rBFJe+mLqK3DoI6QmoTYMotYvHn9W9oBLuqnozhHd6nnC8dMiJy4FcWTQY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=pengutronix.de; spf=pass smtp.mailfrom=pengutronix.de; arc=none smtp.client-ip=185.203.201.7 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=pengutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pengutronix.de Received: from drehscheibe.grey.stw.pengutronix.de ([2a0a:edc0:0:c01:1d::a2]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1syTj3-0007zK-PU; Wed, 09 Oct 2024 12:15:25 +0200 Received: from [2a0a:edc0:0:900:1d::4e] (helo=lupine) by drehscheibe.grey.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1syTj1-000a0s-NJ; Wed, 09 Oct 2024 12:15:23 +0200 Received: from pza by lupine with local (Exim 4.96) (envelope-from ) id 1syTiw-0006sP-1q; Wed, 09 Oct 2024 12:15:18 +0200 Message-ID: <7c9f8ccc145bc9f62d3e5baaab24d1e4f6378436.camel@pengutronix.de> Subject: Re: [PATCH v7 3/6] reset: mchp: sparx5: Map cpu-syscon locally in case of LAN966x From: Philipp Zabel To: Herve Codina , Geert Uytterhoeven , Andy Shevchenko , Simon Horman , Lee Jones , Arnd Bergmann , Derek Kiernan , Dragan Cvetic , Greg Kroah-Hartman , Bjorn Helgaas , Lars Povlsen , Steen Hegelund , Daniel Machon , UNGLinuxDriver@microchip.com, Rob Herring , Krzysztof Kozlowski , Conor Dooley , Saravana Kannan Cc: "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Horatiu Vultur , Andrew Lunn , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Allan Nielsen , Luca Ceresoli , Thomas Petazzoni Date: Wed, 09 Oct 2024 12:15:18 +0200 In-Reply-To: <20241003081647.642468-4-herve.codina@bootlin.com> References: <20241003081647.642468-1-herve.codina@bootlin.com> <20241003081647.642468-4-herve.codina@bootlin.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4-2 Precedence: bulk X-Mailing-List: linux-pci@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-SA-Exim-Connect-IP: 2a0a:edc0:0:c01:1d::a2 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-pci@vger.kernel.org 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. >=20 > In order to avoid the use of the syscon API and so, support for removal, > use a local mapping of the syscon device. >=20 > Link: https://lore.kernel.org/all/20240923100741.11277439@bootlin.com/ [1= ] > Signed-off-by: Herve Codina Reviewed-by: Philipp Zabel regards Philipp