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 994B8C7EE37 for ; Fri, 9 Jun 2023 20:21:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232693AbjFIUVh (ORCPT ); Fri, 9 Jun 2023 16:21:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32950 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232706AbjFIUVG (ORCPT ); Fri, 9 Jun 2023 16:21:06 -0400 Received: from fgw23-7.mail.saunalahti.fi (fgw23-7.mail.saunalahti.fi [62.142.5.84]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 917613C3B for ; Fri, 9 Jun 2023 13:20:06 -0700 (PDT) Received: from localhost (88-113-24-87.elisa-laajakaista.fi [88.113.24.87]) by fgw23.mail.saunalahti.fi (Halon) with ESMTP id ff1d7036-0702-11ee-b972-005056bdfda7; Fri, 09 Jun 2023 23:19:54 +0300 (EEST) From: andy.shevchenko@gmail.com Date: Fri, 9 Jun 2023 23:19:54 +0300 To: Kent Gibson Cc: linux-gpio@vger.kernel.org, brgl@bgdev.pl Subject: Re: [libgpiod][PATCH 2/2] bindings: cxx: examples: fix potential glitch in gpiosetcxx Message-ID: References: <20230609153607.133379-1-warthog618@gmail.com> <20230609153607.133379-3-warthog618@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230609153607.133379-3-warthog618@gmail.com> Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org Fri, Jun 09, 2023 at 11:36:07PM +0800, Kent Gibson kirjoitti: > gpiosetcxx requests lines without setting their output value, and so > sets them all inactive, and subsequently sets them to their requested > value. This can result in glitches on lines which were active and > are set active. > > As this is example code, it is also important to demonstrate that the > output value can be set by the request itself. > > Request the lines with the correct output values set in the request > itself. Same question about commenting in the code. -- With Best Regards, Andy Shevchenko