Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753083AbdFPMFZ (ORCPT ); Fri, 16 Jun 2017 08:05:25 -0400 Received: from mga03.intel.com ([134.134.136.65]:5731 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752619AbdFPMFW (ORCPT ); Fri, 16 Jun 2017 08:05:22 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,347,1493708400"; d="scan'208";a="981640734" Date: Fri, 16 Jun 2017 15:00:48 +0300 From: Mika Westerberg To: "Rafael J. Wysocki" Cc: Gabriele Paoloni , Lorenzo Pieralisi , "Rafael J. Wysocki" , "catalin.marinas@arm.com" , "will.deacon@arm.com" , "robh+dt@kernel.org" , "frowand.list@gmail.com" , "bhelgaas@google.com" , "arnd@arndb.de" , "linux-arm-kernel@lists.infradead.org" , "mark.rutland@arm.com" , "brian.starkey@arm.com" , "olof@lixom.net" , "benh@kernel.crashing.org" , "linux-kernel@vger.kernel.org" , "linux-acpi@vger.kernel.org" , Linuxarm , "linux-pci@vger.kernel.org" , "minyard@acm.org" , John Garry , "xuwei (O)" Subject: Re: [PATCH v9 5/7] ACPI: Translate the I/O range of non-MMIO devices before scanning Message-ID: <20170616120048.GC629@lahna.fi.intel.com> References: <20170606085553.GA20085@red-moon> <20170612155700.GA31930@red-moon> <20170613084831.GP3187@lahna.fi.intel.com> <20170613151013.GT3187@lahna.fi.intel.com> <20170613200339.GX3187@lahna.fi.intel.com> <20170616083313.GY3187@lahna.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 617 Lines: 11 On Fri, Jun 16, 2017 at 01:24:32PM +0200, Rafael J. Wysocki wrote: > > In fact it may be that it is not sufficient in this case because the > > ACPI core might enumerate child devices before the LPC driver even gets > > a chance to probe so you would need to add also scan handler to the > > child devices and mark them already enumerated or something like that. > > Or extend the special I2C/SPI handling to them. Sure but those have I2c/SpiSerialBus() resources which we can use to identify them but for the ipmi thing there is nothing else than _HID so we would need to keep a list of such devices in ACPI core.