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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DF834C7EE23 for ; Tue, 30 May 2023 19:16:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233273AbjE3TQJ (ORCPT ); Tue, 30 May 2023 15:16:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51630 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231374AbjE3TQJ (ORCPT ); Tue, 30 May 2023 15:16:09 -0400 Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 258BC102 for ; Tue, 30 May 2023 12:16:07 -0700 (PDT) Received: by mail-vs1-xe2b.google.com with SMTP id ada2fe7eead31-437de2001bdso1143335137.3 for ; Tue, 30 May 2023 12:16:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20221208.gappssmtp.com; s=20221208; t=1685474166; x=1688066166; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Jso9vHih5+6IaxHyoE18jYidSmiugbdBSe011FzYys0=; b=nt3lyA9yKe2IFAX8DzfpyFJjoan1Vkrz6VMvV+KjgPwf532xcV5PWuVUlFBPuO9DEg bCOOl+ojZIDU/sDdv59+RfwEQfC4kchhY2Byt/lcNZSwzhmY9RpuMH1KEUBRvpqbrKPU 28cdisGVp8R7ekRvyo6ebXyCbOJbAcdyOkcCQVyxiHUejIiQQbfOy1UwAtE2apJl4Dn8 UzDeE0PluyWpOPqlaFulSpTeQJCpAfRQCwW4v+Q5+Zv7pY1YmeA5JSYLuPX0zD00rnDw JjXmS/HtVZsrHyxF6/AwAN7GMwvQyRYgEVsMUZ3VaX9tLrZGCaD+HlTv0iIsxq1nvpps zb5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685474166; x=1688066166; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Jso9vHih5+6IaxHyoE18jYidSmiugbdBSe011FzYys0=; b=h61rD86Tyr/d+eUnrorBim4I/IiwVXZrtGlTniy9e67vBrfkNBOhkn69u8+EYu7qMn tJUZ3s8DOV0yCIfgxLhw8gTsHhsicXktaGa9v3S8G+Alc8gePQRS9F4ce4Ocb74pCCda MP/BXEQ/Rop0SeeRRdt+/woTnqNd7YmeCsolb/i+/XLlf44tMUSxXsof1rXjqcXxTUQv f6UADJknqnQzpgkhBCo5CevgY8JoGcX4GXBA+Yp3GnZ1wjDiJS6YjzN1YmTr9yjgOLOi pMbftODbAbakzcNw8XloJsV1Bm4Ch+u8oxNJ9IMA8i4WfzBXv9j2hexQtIjyR4hA3Cud msLA== X-Gm-Message-State: AC+VfDyOdMAWPlLRHx1ghiBXhk3aYXz00aNmcdUscY4s3GOEidKEPFOg gMfdzW9FlbdLWBBk66PzcLYR+Q1F8Tx9Wf8XPx+mcw== X-Google-Smtp-Source: ACHHUZ5N2LwKgso09mwWA+/M63l/0oFgwj9MsQ6//dZ/DMKciaWGSRkV1i4KVZvS8LImOQY9WolzBXCVch4VWL8DUJs= X-Received: by 2002:a67:fe84:0:b0:434:6d2e:d0ac with SMTP id b4-20020a67fe84000000b004346d2ed0acmr1281192vsr.9.1685474166252; Tue, 30 May 2023 12:16:06 -0700 (PDT) MIME-Version: 1.0 References: <20230530151946.2317748-1-u.kleine-koenig@pengutronix.de> In-Reply-To: From: Bartosz Golaszewski Date: Tue, 30 May 2023 21:15:55 +0200 Message-ID: Subject: Re: [PATCH v2 0/2] gpio: introduce hog properties with less ambiguity To: Kent Gibson Cc: =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , Linus Walleij , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, kernel@pengutronix.de, Andy Shevchenko Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Tue, May 30, 2023 at 5:52=E2=80=AFPM Kent Gibson = wrote: > > On Tue, May 30, 2023 at 05:19:44PM +0200, Uwe Kleine-K=C3=B6nig wrote: > > Hello, > > > > this is another approach after > > https://lore.kernel.org/linux-gpio/20210503210526.43455-1-u.kleine-koen= ig@pengutronix.de > > two years ago. I switched back to "active" and "inactive" from > > "asserted" and "deasserted". The poll about the naming is ambigous, but > > I think with a slight preference of active/inactive over > > asserted/deasserted (with my unbiased self preferring active/inactive, > > too :-) > > > > FWIW, this makes sense to me too - the active/inactive naming is used in > both the GPIO uAPI and libgpiod v2, so it would be consistent with that, > if nothing else. > > Bart, just wondering if gpio-sim should support the aliases as well? > I realise they don't support active-low, so polarity isn't an issue, and > it could even be confusing to support the alias, but just throwing it > out there... > I'm not sure what you need aliases for? Value is only shown, never stored (where you'd need "active", "inactive" strings). Bart