Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965107AbbESOhz (ORCPT ); Tue, 19 May 2015 10:37:55 -0400 Received: from mail-la0-f48.google.com ([209.85.215.48]:32894 "EHLO mail-la0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932990AbbESOhx (ORCPT ); Tue, 19 May 2015 10:37:53 -0400 From: "Grygorii.Strashko@linaro.org" X-Google-Original-From: "Grygorii.Strashko@linaro.org" Message-ID: <555B4ABC.60304@linaro.org> Date: Tue, 19 May 2015 17:37:48 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Linus Walleij CC: Johan Hovold , Alexandre Courbot , "linux-gpio@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] gpiolib: debugfs: display gpios requested as irq only References: <1431696321-7257-1-git-send-email-grygorii.strashko@linaro.org> <20150518110214.GC28127@localhost> <5559E3C0.1040207@linaro.org> <20150518150815.GH28127@localhost> <555A0299.3030803@linaro.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1785 Lines: 47 Hi Linus, On 05/19/2015 05:12 PM, Linus Walleij wrote: > On Mon, May 18, 2015 at 5:17 PM, Grygorii.Strashko@linaro.org > wrote: >> On 05/18/2015 06:08 PM, Johan Hovold wrote: > >>> GPIOs 160-191, platform/4805d000.gpio, gpio: >>> gpio-171 ( ) in hi IRQ-209 >> >> In general agree, but i propose to do it as >> GPIOs 160-191, platform/4805d000.gpio, gpio: >> gpio-171 ((null) ) in hi IRQ-209 >> >> My intention is - this interface could be considered as more or less stable, so >> it is better to add additional information at the end of each line to avoid >> potential breakage of User space SW (test/debug scripts). > > What? If I wanted a stable interface I would use sysfs and document > the ABI in Documentation/ABI/*. > > debugfs is not ABI. > > Debugfs is instable by definition, it is not for production. If tests depend on > it they need to be ready to break and be updated, and in such case > it is a very very good idea to put any such tests in tools/* in the > kernel itself, as does trace-cmd and friends so you can patch the > tests at the same time you patch the code. Okay. Sorry, My comment was not fully correct - keyword was "more or less stable" and of course it is not ABI. Any way, the question is till here - How would it better to do? gpio-171 ( ) in hi IRQ-209 -- or -- gpio-171 ((null) ) in hi IRQ-209 Thanks a lot for your comments. -- regards, -grygorii -- 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/