From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CE0ACC47404 for ; Sat, 5 Oct 2019 17:03:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9CA1B20862 for ; Sat, 5 Oct 2019 17:03:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="Xqf61Bwv" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729348AbfJERDO (ORCPT ); Sat, 5 Oct 2019 13:03:14 -0400 Received: from mail-lj1-f195.google.com ([209.85.208.195]:33271 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725826AbfJERDO (ORCPT ); Sat, 5 Oct 2019 13:03:14 -0400 Received: by mail-lj1-f195.google.com with SMTP id a22so9587137ljd.0 for ; Sat, 05 Oct 2019 10:03:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8ddXseKGv3/4SKLZ5SVHPZUcCGGOrS8Arg9a3AfDJ4U=; b=Xqf61BwvcS/rFfd0wz4vNV9veNGdL7VAfXV8dSdJ9cLhFvhz6TbDdSXAfBl3w+tsEk bE6Se2xBAaoy0VM2T8kU0o1r/pp57sp3P/H7oHuZ4Lz0UQXNuOPUA9nnFYJeHVF6adBz tKqH8jMFJpW0gWbstEwFPhsshv5ay7/rSvwmr+d3hZzhqZZ3fXBFpzrNr3Kf/X/yw6mT +FCpvIaaQdUmgz5HjOnvf2SrTIW8t0J8KyyH6zO3DS95waglbQ2mlSbELrK+FwCgCopv kGWKCDuj0o7xhlUdLR9Pqz/FllWp863da6pdFOsAgeRzi2bmVGTP1Rj4XfBWK1MgguLW AXTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8ddXseKGv3/4SKLZ5SVHPZUcCGGOrS8Arg9a3AfDJ4U=; b=LVryYbgmosoLDkimmwN4xtVUcmIwbjcPNo/qR+AdurNoHE1+zXgQDsrOkDiG93/gDy vJSgVKRU1uVqrsq38DfF05eWBcpnZkuPRHyE08NArbAyW38BsCXMso7r2QC4lr5+8xDf fBrJg+QyGpnxdUYta+lFaH19CJ0sxw487xr8/EprXRgSY2hoHytGW1Oso44o6ieMVo6W fovKsLeAzFTyPCnFvI3vraDoDCcVF/KwiBUgYbJ2EfZvAS8xeOpxpQ0Iiki5ebrRNOky Gw5Emps6RU130SrP553JPWhVBT6Wt7n0pJu1Ht/hbeZGYaV6/K5UYaxMD4qAIfcwnE9b vd6Q== X-Gm-Message-State: APjAAAVVJQoFQGbiAZhIJrsWwOqr9p3an4eV5wljgZB0Q/lOVT2Skoru 7U/VYcmC9syKltzMxkS8puHjGMIUFyUu8R1amiOHWEP6/Ew= X-Google-Smtp-Source: APXvYqwx2pmDu6fo2GmW7KjDXSgU9KCpAgfn1umVPmNgf9cwxEakvOiLABhSZCeVxH+vPM/w25JxcW7jjbz4fyLAQNY= X-Received: by 2002:a2e:5dc3:: with SMTP id v64mr13342905lje.118.1570294990791; Sat, 05 Oct 2019 10:03:10 -0700 (PDT) MIME-Version: 1.0 References: <20190921102522.8970-1-drew@pdp7.com> In-Reply-To: From: Linus Walleij Date: Sat, 5 Oct 2019 19:02:58 +0200 Message-ID: Subject: Re: [RFC] gpio: expose pull-up/pull-down line flags to userspace To: Bartosz Golaszewski Cc: Drew Fustini , "open list:GPIO SUBSYSTEM" , Thomas Petazzoni Content-Type: text/plain; charset="UTF-8" Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Fri, Oct 4, 2019 at 9:22 AM Bartosz Golaszewski wrote: > The config ioctl (or > something similar) you're mentioning may appear sooner actually - > users of libgpiod have been requesting a way of changing the direction > of a line without releasing it - something that's possible in the > kernel, but not from user-space at the moment. I'll submit something > that allows to change the configuration of a requested line soon. Hm! I guess I assumed that userspace users would be using the lines for either input or output, not complex use cases like that, reversing direction and what not. What kind of usecase is this? I certainly hope nothing like doing userspace drivers for complex hardware ... those should be in the kernel... the current ABI is a bit oriented around industrial automation and prototyping use cases. Yours, Linus Walleij