From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [PATCH v3] gpiolib: return -ENOENT if no GPIO mapping exists Date: Wed, 11 Dec 2013 16:16:07 +0200 Message-ID: <20131211141607.GJ2281@intel.com> References: <1386729148-16262-1-git-send-email-acourbot@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mga02.intel.com ([134.134.136.20]:45486 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751133Ab3LKOJs (ORCPT ); Wed, 11 Dec 2013 09:09:48 -0500 Content-Disposition: inline In-Reply-To: <1386729148-16262-1-git-send-email-acourbot@nvidia.com> Sender: linux-gpio-owner@vger.kernel.org List-Id: linux-gpio@vger.kernel.org To: Alexandre Courbot Cc: Linus Walleij , Andy Shevchenko , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org On Wed, Dec 11, 2013 at 11:32:28AM +0900, Alexandre Courbot wrote: > Some devices drivers make use of optional GPIO parameters. For such > drivers, it is important to discriminate between the case where no > GPIO mapping has been defined for the function they are requesting, and > the case where a mapping exists but an error occured while resolving it > or when acquiring the GPIO. > > This patch changes the family of gpiod_get() functions such that they > will return -ENOENT if and only if no GPIO mapping is defined for the > requested function. Other error codes are used when an actual error > occured during the GPIO resolution. > > Signed-off-by: Alexandre Courbot > Reviewed-by: Andy Shevchenko Reviewed-by: Mika Westerberg