From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-lf0-x22a.google.com ([2a00:1450:4010:c07::22a]) by bombadil.infradead.org with esmtps (Exim 4.87 #1 (Red Hat Linux)) id 1dDmNt-0006NF-RK for barebox@lists.infradead.org; Thu, 25 May 2017 06:36:35 +0000 Received: by mail-lf0-x22a.google.com with SMTP id 99so78476958lfu.1 for ; Wed, 24 May 2017 23:36:12 -0700 (PDT) References: <20170522152420.14443-1-andrew.smirnov@gmail.com> <20170522152420.14443-2-andrew.smirnov@gmail.com> <1495649778.5146.219.camel@kymetacorp.com> From: Nikita Yushchenko Message-ID: <38ca9996-beb8-19a2-99ee-2a4fa7a82232@cogentembedded.com> Date: Thu, 25 May 2017 09:36:09 +0300 MIME-Version: 1.0 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH 2/4] gpiolib: Add code to support "active low" GPIOs To: Andrey Smirnov , Trent Piepho , Sascha Hauer Cc: "barebox@lists.infradead.org" , "cphealy@gmail.com" > IMHO, whether any of likes it or not, OF_GPIO_ACTIVE_LOW is an > existing feature and the only technical question is if it should be > supported by Barebox on per-driver basis or if there should be a > central API for it. > > Sascha, are you still OK with me proceeding with making and using an > API, or should I just scrap that and handle this as a part of my > "usb-no-xcev"? Is support for case when this usb-no-xcev's gpio is active high needed? If yes, then your questions above are valid. If no, then there is third option, completely ignore this aspect of device tree and just assume that gpio is active low. _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox