From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 6B72436A036; Thu, 21 May 2026 16:27:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779380835; cv=none; b=VpAIgQQIpIiKy3nd27gC4C5ZNe1spiLvoLtT5cgjWdNUxyBRDvG6aVrIKRbZ2dR57Of9HN6rSHMHXghcroMZTFi1+yIzAgGdk5dVoq1fR4yhuKxMJ7BVF+mwV38EYEyCeSXFjz7nFqSMpJwQkrAxNBk4yDzCLdHDkHC9eKbnlEQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779380835; c=relaxed/simple; bh=C8Y+Ik99+HGvqZnOH/2fxPU97x5XHCh7WTq1PSR2UWA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=hGr8TfoV2W+ZcvbxvPgkPTd6JDzhQiOANJUR/QauEzDnWRUQhuNk4amxLEYQSmNnL7aBvyJn4ybtwMUSDX8N4em6wOMUXYKGc5Hrt61uAU84KPFoRyfhbJq1lPQn/6dZhXTa3Qt/4sFBvNzOVCvsB+rsNzJYh5DHyLcdK1kYrmo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=DuOoRKBO; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="DuOoRKBO" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9F61F1F000E9; Thu, 21 May 2026 16:27:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779380834; bh=en35R6sc2ImIXJjSfKNTDeODIfFRRIXQVjpIv7bHdmk=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=DuOoRKBO6Y1Oqrq2sJVjpuELojujcFM80db44IMaa6rdCsVyxoL2s+9M7w0kvfCxY WCW3FPjEQbdO3j0DQ1pU/39D2T4/mSgwGY/XxIKOZ99G52iza5+52jIdv/FZfUwWIi TKQELjriOStYA3QCfXpiFucHhhGpZQeGtMu3ZBtbfP5D+Mh8Zt2LZ1PGhN+qPrI0aw 6xkmpJjoMLOWpnx9ml1tKtw54ghGgcDQUD309KlAWUMHkk31otLpmnySG1nt0I98cR ccI4arI3xtm1COLpzPFvlggMBVkYkf2XDAzZguFVzH0ETgrlum/YGVLx6H8Y1F9dOB BCKRbLLME2zqQ== Date: Thu, 21 May 2026 17:27:05 +0100 From: Lee Jones To: Bartosz Golaszewski Cc: Shivendra Pratap , Sebastian Reichel , Mark Rutland , Lorenzo Pieralisi , "Rafael J. Wysocki" , Daniel Lezcano , Christian Loehle , Ulf Hansson , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Bjorn Andersson , Konrad Dybcio , Arnd Bergmann , Souvik Chakravarty , Andy Yan , Matthias Brugger , John Stultz , Moritz Fischer , Sudeep Holla , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Florian Fainelli , Krzysztof Kozlowski , Dmitry Baryshkov , Mukesh Ojha , Andre Draszik , Greg Kroah-Hartman , Kathiravan Thirumoorthy , Srinivas Kandagatla , Bartosz Golaszewski Subject: Re: [PATCH v22 08/13] mfd: core: Add firmware-node support to MFD cells Message-ID: <20260521162705.GH3591266@google.com> References: <20260514-arm-psci-system_reset2-vendor-reboots-v22-0-28a5bde07483@oss.qualcomm.com> <20260514-arm-psci-system_reset2-vendor-reboots-v22-8-28a5bde07483@oss.qualcomm.com> <20260521112638.GD2921053@google.com> <20260521132419.GA3591266@google.com> 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-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Thu, 21 May 2026, Bartosz Golaszewski wrote: > On Thu, May 21, 2026 at 3:24 PM Lee Jones wrote: > > > > > > > > I suggested it because of its flexibility. The alternative I had in > > > mind is something like a new field in mfd_cell: > > > > > > const char *cell_node_name; > > > > > > Which - if set - would tell MFD to look up an fwnode that's a child of > > > the parent device's node by name - as it may not have a compatible. > > > > Remind me why the chlid device can't look-up its own fwnode? > > > > Oh sure it can, but should it? I'm not sure it's logically sound to > have the child device reach into the parent, look up the fwnode and > then assign it to itself after it's already attached to the driver. > This should be done at the subsystem level before the device is > registered. Leaf drivers reach back into the parent all the time. -- Lee Jones