From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) (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 E9BECEAC7; Fri, 12 Jul 2024 13:34:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.70.183.194 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720791293; cv=none; b=aAkq6+iK3JWXYZ8tJ3zCmu9SWJrUVFke/ajuZM9zxU+eGy7awbUld+Zz+uvPS0Z6zhk1BcdnSvvUBZL/HK6sihnOIkHsbFkaW8YsCRz3lCJdrFfupAcgEL7KWDGmGxTzhhg6M7OugTaCGTg0I8llJeeVFW8Ft9gGWBP5rK6vsFI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720791293; c=relaxed/simple; bh=yLguL9IS/tTpZo82sbn8FxthUie+o8Bk4E2qK1Cergs=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=p7Gcvs+5lsJbt3UBpW66MaNrNz6gEgIZ94dxxJcrXfcvRB+KSoF6SmSL3GwTa7N3y8FFR8ROzEWyUh0jjzHepOYrpj6ipVjCaLN/8j5j1GbqJtumRmiZfqPZC2rznWANWHTSFEoYfJPN1XX6S0pXM8OqMukHgjiX/GWk6Nwj430= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=BVODHXoM; arc=none smtp.client-ip=217.70.183.194 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="BVODHXoM" Received: by mail.gandi.net (Postfix) with ESMTPSA id 0B28F40002; Fri, 12 Jul 2024 13:34:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1720791289; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=zsIQ40b9k5VvrZKyuXL7OJ2FO+xOflyP76hRNF0J6zA=; b=BVODHXoMJ06+cRjiYiP5PkKZqMfnTd0SHEHEZ/AbF5SbGOmDuiz+FsyWyYeHKo9ohZbicb 5ODll117HMaIK+GgBbfJLlQ2bWtcXYNRlFa3OvVhmtmwL5uEp9/wgeWfFYpho70ZAqSHoR vY8YY0wAp0i8CBGh2T8+lLhWxXvLTzQ3i8sWcAe8Wp31VEGXv4nyukDwEiJN222Eg2yMFZ aKceAkB79SYoexDrzd5alr4Idb5IrMGjOHHjT6PjPqVipmOQHr4GDPzJfA/F8vLLDqw2ip vom/FeYbQErkaKIAettZJwR+bw8tmxCpe4a8dCe7Rc/H1nJm+Uo4P6w7hAD5aQ== Date: Fri, 12 Jul 2024 15:34:46 +0200 From: Herve Codina To: Saravana Kannan Cc: Greg Kroah-Hartman , "Rafael J. Wysocki" , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Wolfram Sang , Rob Herring , Mark Brown , Len Brown , Andy Shevchenko , Daniel Scally , Heikki Krogerus , Sakari Ailus , Geert Uytterhoeven , kernel-team@android.com, Wolfram Sang , linux-kernel@vger.kernel.org, imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-spi@vger.kernel.org, linux-acpi@vger.kernel.org, Luca Ceresoli , Thomas Petazzoni Subject: Re: [PATCH v3 0/2] fw_devlink overlay fix Message-ID: <20240712153446.37e26d34@bootlin.com> In-Reply-To: <20240423103924.366eba43@bootlin.com> References: <20240411235623.1260061-1-saravanak@google.com> <20240423103924.366eba43@bootlin.com> Organization: Bootlin X-Mailer: Claws Mail 4.2.0 (GTK 3.24.41; x86_64-redhat-linux-gnu) Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-GND-Sasl: herve.codina@bootlin.com Hi Saravana, On Tue, 23 Apr 2024 10:39:24 +0200 Herve Codina wrote: > Hi Saravana, > > On Thu, 11 Apr 2024 16:56:20 -0700 > Saravana Kannan wrote: > > > Overlays don't work correctly with fw_devlink. This patch series fixes > > it. This series is now ready for review and merging once Geert and Herve > > give they Tested-by. > > > > Geert and Herve, > > > > This patch series should hopefully fix both of your use cases [1][2][3]. > > Can you please check to make sure the device links created to/from the > > overlay devices are to/from the right ones? > > > > Thanks, > > Saravana > > > > I tested the series. > > On my Microchip use case (i.e. DT overlay on a PCIe device), I observed that > some driver removal were done in a wrong order. For instance, the onboard > PCIe device interrupt controller (oic@e00c0120) was removed before its > consumers. > > I enabled debug traces in core.c and observed that many links were dropped. > These links are related to pinctrl, clock, reset, interrupts, ... > I have the feeling that these links should not be dropped. > Have you made any progress on this topic ? I haven't seen any updates. Maybe I missed something. Best regards, Hervé