From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [RFC 00/15] ACPI graph support Date: Thu, 6 Oct 2016 12:11:33 +0300 Message-ID: <20161006091133.GF30800@lahna.fi.intel.com> References: <1475621148-21427-1-git-send-email-sakari.ailus@linux.intel.com> <20161005092215.GA20248@red-moon> <20161005114129.GI1765@lahna.fi.intel.com> <20161005150641.GA22282@red-moon> <20161005153229.GO1765@lahna.fi.intel.com> <20161005161800.GA22433@red-moon> <20161006085703.GA22776@red-moon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mga06.intel.com ([134.134.136.31]:38079 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966505AbcJFJLk (ORCPT ); Thu, 6 Oct 2016 05:11:40 -0400 Content-Disposition: inline In-Reply-To: <20161006085703.GA22776@red-moon> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Lorenzo Pieralisi Cc: "Rafael J. Wysocki" , Sakari Ailus , ACPI Devel Maling List , Mark Rutland , Mark Brown , Rob Herring , Al Stone On Thu, Oct 06, 2016 at 09:57:03AM +0100, Lorenzo Pieralisi wrote: > I am trying to understand why x86 wants to do this, please understand > our point of view too, we do not want to block progress we want to > prevent a mess. One reason is that we have boards like Joule where developers are allowed to connect different peripherals using buses such as I2C and SPI where there is no native enumeration mechanism. This includes camera sensors and related so there needs to be a way for a developer to describe this in ACPI. Just as can be done when using ARM and DT.