From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759431AbcDETQV (ORCPT ); Tue, 5 Apr 2016 15:16:21 -0400 Received: from mail-wm0-f48.google.com ([74.125.82.48]:36543 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757214AbcDETQT (ORCPT ); Tue, 5 Apr 2016 15:16:19 -0400 MIME-Version: 1.0 In-Reply-To: <20160405183255.GH1924@sirena.org.uk> References: <20160331172935.GL2350@sirena.org.uk> <20160401140856.GW2350@sirena.org.uk> <20160402162449.GB2350@sirena.org.uk> <20160404160327.GH2350@sirena.org.uk> <20160405183255.GH1924@sirena.org.uk> Date: Tue, 5 Apr 2016 22:16:16 +0300 Message-ID: Subject: Re: [RFC PATCH 06/10] spi: add support for ACPI reconfigure notifications From: Octavian Purdila To: Mark Brown Cc: "Rafael J. Wysocki" , "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 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 5, 2016 at 9:32 PM, Mark Brown wrote: > On Tue, Apr 05, 2016 at 02:49:13PM +0300, Octavian Purdila wrote: > >> If we really want to have a single path for ACPI enumeration we could >> do that by using an ACPI SPI bridge driver or scan handlers after >> extending the matching mechanisms. But we would still need to modify >> the SPI subsystem and I don't think its worth it just to save a call >> to acpi_register_spi_devices() from spi_register_master(). > > It's not specifically for SPI, it's the fact that you're asking every > single bus type which might be described in ACPI to handle both hotplug > and coldplug paths separately. Given that the code that's being added > just seems like trivial boilerplate it seems like we're doing this > wrong, we should be factoring this out so there's nothing bus types can > get wrong. > AFAICS this is exactly the same case for DT: one code path for coldplug and one for hotplug. Which makes me think that it is not possible to have a single path for both, or maybe its not worth it. Do I miss something obvious?