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 3D4EBC3DA78 for ; Sat, 14 Jan 2023 11:20:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229723AbjANLUV (ORCPT ); Sat, 14 Jan 2023 06:20:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52078 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229655AbjANLUU (ORCPT ); Sat, 14 Jan 2023 06:20:20 -0500 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 26FC19D for ; Sat, 14 Jan 2023 03:20:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1673695217; x=1705231217; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=ClOncuvbpI4fydrfg4PEzgCfy9sXaBnPdlTzKWAtMZA=; b=g3m6w/xnG1+gJ3f7Oxz6K2UAc8PovPZfO4LtL6GfjjD/td7AVkkHU4Ox mNykFeoG+iiYp68PUyM60xdFZNWGdXezOnT0acFUv7XVvAlp+Rx30f4ty XHOPclLI/RyHZo1bvCPDmzAZ2uTeA+HumLsHGCrm5MjsJdRIgRuYVWMwV etmwyFFnhE+YwTwrBdJ/0IkQiRbgFtZxiFuGYSLLclCsfddPdObSrbnZg 1C2H4UmdtBCZZtQnfqh1U25pBWUvALFzaPtNEMMa6F9AVvw7qQyt2ZVh7 lGBMCFT7CPe5/FNISCMqJ6RfS6wggtksAT+SMkn7mx684Ex/tkGReUVCn Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10589"; a="307736038" X-IronPort-AV: E=Sophos;i="5.97,216,1669104000"; d="scan'208";a="307736038" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Jan 2023 03:20:16 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10589"; a="832342558" X-IronPort-AV: E=Sophos;i="5.97,216,1669104000"; d="scan'208";a="832342558" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga005.jf.intel.com with ESMTP; 14 Jan 2023 03:20:14 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1pGea5-0097lr-1S; Sat, 14 Jan 2023 13:20:13 +0200 Date: Sat, 14 Jan 2023 13:20:13 +0200 From: Andy Shevchenko To: Bartosz Golaszewski Cc: Kent Gibson , Linus Walleij , Viresh Kumar , linux-gpio@vger.kernel.org, Bartosz Golaszewski Subject: Re: [libgpiod][PATCH 12/16] bindings: cxx: add line_config.set_output_values() Message-ID: References: <20230113215210.616812-1-brgl@bgdev.pl> <20230113215210.616812-13-brgl@bgdev.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230113215210.616812-13-brgl@bgdev.pl> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Fri, Jan 13, 2023 at 10:52:06PM +0100, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Extend line_config to expose a new method - set_output_values() - which > wraps the new C function for setting multiple output values at once. ... Side Q: Does documentation describe the order in which lines are being set? Or is it solely specified by a kernel driver for a hardware? (I can imagine that this may be not so trivial as long as the input parameters, i.e. line offsets, are not sorted and hardware supports full bank atomic write, this may have a lot of interesting side effects.) -- With Best Regards, Andy Shevchenko