From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751927AbbCGWNK (ORCPT ); Sat, 7 Mar 2015 17:13:10 -0500 Received: from mail-ob0-f173.google.com ([209.85.214.173]:45231 "EHLO mail-ob0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751284AbbCGWNG (ORCPT ); Sat, 7 Mar 2015 17:13:06 -0500 MIME-Version: 1.0 In-Reply-To: <20150225182502.GA7586@psi-dev26.jf.intel.com> References: <1418890998-23811-1-git-send-email-heikki.krogerus@linux.intel.com> <4078818.ecVtLF3hjd@vostro.rjw.lan> <20150224203459.GC13094@psi-dev26.jf.intel.com> <20150225182502.GA7586@psi-dev26.jf.intel.com> Date: Sat, 7 Mar 2015 23:13:05 +0100 Message-ID: Subject: Re: [RFC PATCH] gpio: support for GPIO forwarding From: Linus Walleij To: David Cohen Cc: Alexandre Courbot , "Rafael J. Wysocki" , Heikki Krogerus , "Rafael J. Wysocki" , Darren Hart , Arnd Bergmann , Andy Shevchenko , Mika Westerberg , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" , ACPI Devel Maling List 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 Wed, Feb 25, 2015 at 7:25 PM, David Cohen wrote: > In my case [1] I need 2 "virtual devices" (and more in future) to be > part of an USB OTG port control. I call it virtual because they are too > simple components connected to no bus and controlled by GPIOs: > - a fixed regulator controlled by GPIO > - a generic mux controlled by GPIO > > I'd need to request official ACPI HID for them in order to make them > self-sufficient. > > I can go ahead with this approach, but we have many examples of drivers > on upstream that are platform driver expecting to receive gpio via > platform data (e.g. extcon-gpio). The ACPI table of some products on > market were defined following this concept and won't change anymore. So it's not just going to be GPIOs I take it? There is going to be regulator forwarding, clock forwarding, pin control forwarding, IRQ forwarding and DMA channel forwarding etc at the end of the day? I think it's strange that we see this so much, is the real problem that ACPI and the kernel have different ideas of what constitutes a device? And how come the DT seems to be a much better fit and not experience this? Because we haven't had to deal with deployed device trees with resources (GPIOs, regulators, etc) bound to some complex MFD device? Yours, Linus Walleij