From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752021AbcDZKXc (ORCPT ); Tue, 26 Apr 2016 06:23:32 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:43802 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751873AbcDZKXa (ORCPT ); Tue, 26 Apr 2016 06:23:30 -0400 Date: Tue, 26 Apr 2016 11:23:14 +0100 From: Mark Brown To: Lu Baolu Cc: felipe.balbi@linux.intel.com, Mathias Nyman , Greg Kroah-Hartman , Lee Jones , Heikki Krogerus , MyungJoo Ham , Chanwoo Choi , Liam Girdwood , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Message-ID: <20160426102314.GS3217@sirena.org.uk> References: <1461571496-9600-1-git-send-email-baolu.lu@linux.intel.com> <1461571496-9600-5-git-send-email-baolu.lu@linux.intel.com> <20160425173024.GO3217@sirena.org.uk> <571ED178.4090700@linux.intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vhjys16BnDfiwTH0" Content-Disposition: inline In-Reply-To: <571ED178.4090700@linux.intel.com> X-Cookie: Tomorrow, you can be anywhere. User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v6 04/10] regulator: fixed: add support for ACPI interface X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --vhjys16BnDfiwTH0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 26, 2016 at 10:24:56AM +0800, Lu Baolu wrote: > The GPIO name might be different in different use cases. For my case, > it is "vbus_en", but other cases should use the different name. > On ACPI compatible platforms, GPIO resources are reported via ACPI > tables and (devm_)gpiod_get() hides the APCI complexity and returns > the gpiod according to "gpio_name". That's labelling that you might want to do on the supplier side or at system level. Why does the device care? It's requesting the GPIO in its own context and it's only requesting one GPIO, with DT we're just always calling the GPIO "gpio" which works fine. --vhjys16BnDfiwTH0 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXH0GRAAoJECTWi3JdVIfQ5zwH/iXg5QyXjM9gNMFPuPdhfHeq y3v+3QOZ0fb6saV2JQd3zfsQD71uKQzr/rOiLx1TPGOr0HcaTBgX8BdP2E5moX9Q hnSc33pqB4dh2ppIdKwMLyUSqK/mbKLLtL9WiIb7b2NTPsqhEIntYupkhyI9EN5F CrDUTnbxc+xQczCYQvHS5LePZoPkH5F1v0OBwv929Ltt77spcShMHfgXGRJc3K3E 4cKdiSzJfeYcHYwa8YoeD9dUumS3tDGQq1cwH4ci0PDZ0SK2FQsuBSSd8IXxKTtO Jry5zA75xHtCYfzxjV9sTr05f4BbMx06vDeYBUsf2YdloA9xVmxRLXiI5s1G59M= =RUIh -----END PGP SIGNATURE----- --vhjys16BnDfiwTH0--