Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752504AbcDBQZP (ORCPT ); Sat, 2 Apr 2016 12:25:15 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:38154 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751314AbcDBQZL (ORCPT ); Sat, 2 Apr 2016 12:25:11 -0400 Date: Sat, 2 Apr 2016 09:24:49 -0700 From: Mark Brown To: "Rafael J. Wysocki" Cc: Octavian Purdila , "Rafael J. Wysocki" , Len Brown , Matt Fleming , Wolfram Sang , Joel Becker , Christoph Hellwig , "linux-acpi@vger.kernel.org" , linux-efi@vger.kernel.org, linux-i2c , linux-spi@vger.kernel.org, lkml , Irina Tirdea Message-ID: <20160402162449.GB2350@sirena.org.uk> References: <1459417026-6697-1-git-send-email-octavian.purdila@intel.com> <1459417026-6697-7-git-send-email-octavian.purdila@intel.com> <20160331172935.GL2350@sirena.org.uk> <20160401140856.GW2350@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rtWt6SZ6GqpxALBD" Content-Disposition: inline In-Reply-To: X-Cookie: If anything can go wrong, it will. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 216.2.64.20 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [RFC PATCH 06/10] spi: add support for ACPI reconfigure notifications 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 Content-Length: 1576 Lines: 40 --rtWt6SZ6GqpxALBD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Apr 01, 2016 at 09:26:38PM +0200, Rafael J. Wysocki wrote: > On Fri, Apr 1, 2016 at 4:08 PM, Mark Brown wrote: > > That's not the point. The point is that since the handling is identical > > why are we handling it through exactly the same code? > I think that during the initial enumeration the controller driver's > probe walks the children and creates device objects for them. When a > table is loaded later, the controller driver has been probed already > and there needs to be a way to trigger a walk over the (new) children > from it. > Or a hook somewhere around acpi_platform_notify() is needed. What I don't understand is why the flow on inital probe isn't simply to register the controller which then triggers the walk of the children. That way any bus that supports initial probe also supports hotplug without needing to go and manually add a second code path. --rtWt6SZ6GqpxALBD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW//JQAAoJECTWi3JdVIfQFHwH/2J7wKNmy+CXSc+JOI24dd/l BsStLIDa+Vh7k9Ml720D1EoA1NwZxKkMV2wmEMSrYBGwrIAVJr46l2L9sYo1nyzU mTxlwWVPbbgr5ofF/RlaJrXFI3eIogBoXrrrPk54WrizG1W5LvNNn2xtzLJlHxGa 8olcz/UKlydNVA0n8y/8QR+Rg+uy6MULLqgpoTig0P5Hck6/E7gNG+gYZhwVA5yI Ak4/HAe1BPdxaYUuf/rYqeRYLlXv4jPqZER5CTSPP/cU64XSns3S0AI8LXrgXFBV DFCEvNpXoMKYpxCoXlzttIbPBgjP9mdiiVz2rL+JYkjTI0jwMHqRh4DvNDRoG8U= =Kt7q -----END PGP SIGNATURE----- --rtWt6SZ6GqpxALBD--