Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751295AbbHQTAu (ORCPT ); Mon, 17 Aug 2015 15:00:50 -0400 Received: from mail-pa0-f42.google.com ([209.85.220.42]:34150 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751033AbbHQTAr (ORCPT ); Mon, 17 Aug 2015 15:00:47 -0400 Date: Mon, 17 Aug 2015 12:00:45 -0700 From: Dustin Byford To: Mika Westerberg Cc: Wolfram Sang , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, rjw@rjwysocki.net, linux-acpi@vger.kernel.org Subject: Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels Message-ID: <20150817190045.GA25318@cumulusnetworks.com> References: <1439510358-16664-1-git-send-email-dustin@cumulusnetworks.com> <1439580693-5538-1-git-send-email-dustin@cumulusnetworks.com> <20150817120305.GB1552@lahna.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150817120305.GB1552@lahna.fi.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1700 Lines: 49 Hi Mika, Thanks for taking a look. On Mon Aug 17 15:03, Mika Westerberg wrote: > On Fri, Aug 14, 2015 at 12:31:32PM -0700, Dustin Byford wrote: > > Name (_DSD, Package () > > { > > ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), > > Package () { > > Package (2) { "compatible", "nxp,pca9548" }, > > } > > Nice, you are using _DSD :-) Yes, and I've got some other patches related to that. I'll keep sending, but the relative youth of _DSD does bring up a few higher level issues (for me at least). One thing at a time though, stay tuned. > > I had to: > > > > 1) Find and set an ACPI companion for the "virtual" I2C adapters created > > for each mux channel. > > > > 2) Make sure to scan adap.dev when registering devices under each mux > > channel. > I think the current code in I2C core is not actually doing the right > thing according the ACPI spec at least. To my understanding you can have > device with I2cSerialBus resource _anywhere_ in the namespace, not just > directly below the host controller. It's the ResourceSource attribute > that tells the corresponding host controller. I think you're right. > I wonder if it helps if we scan the whole namespace for devices with > I2cSerialBus that matches the just registered adapter? Something like > the patch below. Looks reasonable to me. Let me work with the patch for a bit and see if I can make it work in my system. --Dustin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/