From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1424130AbcFHWYb (ORCPT ); Wed, 8 Jun 2016 18:24:31 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:51594 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422636AbcFHWYa (ORCPT ); Wed, 8 Jun 2016 18:24:30 -0400 Date: Wed, 8 Jun 2016 23:24:02 +0100 From: Mark Brown To: "Rafael J. Wysocki" Cc: "Rafael J. Wysocki" , Linux PM list , Greg Kroah-Hartman , Linux Kernel Mailing List , Alan Stern , Grant Likely , Rob Herring , Tomeu Vizoso , Thierry Reding , Dmitry Torokhov , Geert Uytterhoeven , Michael Turquette Message-ID: <20160608222402.GQ7510@sirena.org.uk> References: <1623682.7KVblAB3KQ@vostro.rjw.lan> <2576341.476ZsjkPgF@vostro.rjw.lan> <1816598.SuJvGrVRJK@vostro.rjw.lan> <20160608124844.GH7510@sirena.org.uk> <20160608183535.GP7510@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fTD7sGci972winw4" Content-Disposition: inline In-Reply-To: X-Cookie: We've upped our standards, so up yours! User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [RFC][PATCH 2/5] driver core: Functional dependencies tracking support X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --fTD7sGci972winw4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Jun 08, 2016 at 10:48:23PM +0200, Rafael J. Wysocki wrote: > On Wed, Jun 8, 2016 at 8:35 PM, Mark Brown wrote: > > A parent (especially a MFD) may create a child to fulfil a role that > > could also be filled by a non-parent device, if that happens then > > depending on what ends up creating these links (it's not 100% clear from > > this series) it's likely that the link creation will also end up > > registering a dependency unless we do something special. Now I think > > about it this does depend on how we create the children though, it's > > less likely to be an issue if the dependencies are created by firmware > > code. > If that's a non-child device, I would expect it to exist beforehand No, it's an actual child. --fTD7sGci972winw4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXWJsAAAoJECTWi3JdVIfQ8bgH/1HZg7hwOBXyYUJOZ4+eOSL6 P3CV86Og7IuUcrHJ0JQBXL5uJmb000hgbFKv9AGhw4HLHyivn5iAU1SOgEMt2D4g wPXSxYytGNGU9a2Q6i+2a/I0AAsLwIKSzAtvmRbTjVVbtMyfbmTUeyKE6+JFhzz7 z6q+iEEnb7OMmPlgDUbalKn6/lh1mnnqym/+52hLMfSgGRa/8fbhO2juRcj9GP9i WgGTffpP9VFLBIKBPcBJAUdqeq/Cw/IXB29tYqygCeW4u1Jf/oqGTCV6k9g6tyao n79y4JyHQAGw0miYDcmr2IrknRjCOF6SC2CFiOXGdgq2z86dObec/Am/xHgEs6E= =Q9u4 -----END PGP SIGNATURE----- --fTD7sGci972winw4--