From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752735AbcKXXZA (ORCPT ); Thu, 24 Nov 2016 18:25:00 -0500 Received: from mail-qt0-f175.google.com ([209.85.216.175]:36366 "EHLO mail-qt0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751136AbcKXXYv (ORCPT ); Thu, 24 Nov 2016 18:24:51 -0500 MIME-Version: 1.0 In-Reply-To: <20161124163231.GD26657@ulmo.ba.sec> References: <1478083719-14836-1-git-send-email-smangipudi@nvidia.com> <0e3e89a8-a2f1-68c2-0586-58902fb91587@wwwdotorg.org> <20161122173042.GA3239@ulmo.ba.sec> <20161123194036.GA25876@ulmo.ba.sec> <20161124163231.GD26657@ulmo.ba.sec> From: Linus Walleij Date: Fri, 25 Nov 2016 00:24:50 +0100 Message-ID: Subject: Re: [PATCH] gpio: tegra186: Add support for T186 GPIO To: Thierry Reding Cc: Stephen Warren , Suresh Mangipudi , Laxman Dewangan , Alexandre Courbot , "linux-kernel@vger.kernel.org" , "linux-gpio@vger.kernel.org" , "linux-tegra@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mostly it seems we are in understanding here, looking forward to the patches... On Thu, Nov 24, 2016 at 5:32 PM, Thierry Reding wrote: > On Thu, Nov 24, 2016 at 04:08:08PM +0100, Linus Walleij wrote: >> I don't understand. Userspace should have no concern about the >> numberspace. Lines can be named from DT or ACPI so you can >> look up line chip+offset from the names. > > Userspace would have to know about the numberspace if it wants to use > the character device, right? No it shouldn't really. Adding gpio-line-names = "foo", "bar" etc and following a reasonable naming policy (such as using the rail names on the schematic, which is usually helpful) the GPIO can easily be looked up from its name. The chardev tries to overcome the hardships in finding the GPIO you want this way. Yours, Linus Walleij