From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C0EE3A054A; Wed, 8 Jun 2022 11:03:20 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6A9DE40689; Wed, 8 Jun 2022 11:03:20 +0200 (CEST) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id F019F4021D for <dev@dpdk.org>; Wed, 8 Jun 2022 11:03:18 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id A3B873200992; Wed, 8 Jun 2022 05:03:17 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 08 Jun 2022 05:03:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1654678997; x= 1654765397; bh=XWb5SLjzFL3NMamDynNW3xk2RiU+2C878oaZysjKjBA=; b=B Su5dUzHcEHqHIHlRPrwn9I3UOISgNSZgxrjitdUipL9Z1ckap5eoqTz/REHeCOCp GJ6QJxJyuWEQYWn8YtOi/ky57vx+5wMtbdCuiANcmK73QKmANwgGC3ByF9L0lxa/ onR4na4kGEL1Wp4sME5EIrGOyCEox8EIGnfH0begAOjA3oa13XNA1/tZF+MGaxYf 9hPWCag9mGozftxv/gDfkXf1d+mVJbfHtmZrm/KEM9nYdls5ELrKloIYtrfwO/Yr cBvlOW9/GB94IpvhKzy/6vx8bgXVfyoHfBKahVXAtMZSn5f71Zg+Vqt+AMLSEW6J JjF2ZYis8CyovjRbDlnvg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1654678997; x= 1654765397; bh=XWb5SLjzFL3NMamDynNW3xk2RiU+2C878oaZysjKjBA=; b=V 7SyuXCpHUjVhmqBPlB8RF6PKXX5oDVdDRDZVyDaZNm6LEQWltKSiwcVgC/LPSaD+ gwYwDU/dxoZEL2uUEIg32cCTAQv5tRWzXWOyVrnNSFunRDb/K2UDptct4kmjRqUs Koh9og6bCuU1VJPxh5ODE7hi7tVg+Cb2dAYLL6KiE5D9uUCKrszynOkzI0EJWTKN Y30jT7W8nCXBR9UH2VRZH9O0rNQLFr7+7vIHhf8MwbMqxrwhT1+MbvNrfKtHEDVA 0ndB6KLt42MMiRlW6axPx9GWJndM9Z/aGosVVxrWKLSAusv8MCVrKJMjITUq0C++ oEfrtqrjJ0jwg+zt48vEA== X-ME-Sender: <xms:1GWgYoaib9m9uMTp15yxW4FJLxoP5HA3DBftWeBOr5lWzzk935wOKQ> <xme:1GWgYjazCjDVbEQm4XLhXHdv3TlwwPjcKjuBrQGWDiQXN4hV0ZGW9UPl_lr9oF27f 29CvPYDmNBT8UjP-A> X-ME-Received: <xmr:1GWgYi8quRLLGHA-l3ep8G32gX30U_siccHLmdvdTY7mq-1bLMTwWriV6mrLnX4pWAgzw0kqaApf5BZHoOSURBh-bQ> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedruddtjedgtdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: <xmx:1WWgYiqc9D6CQC0IzdKHx14Z5J0zg8RmpuvzoUSffFKqS_kNaGq6FQ> <xmx:1WWgYjr-bzGTnbn2GGF_-1GPzx57StEdvXQVoCss_TWaiZEIZ_RPQQ> <xmx:1WWgYgT3ddU7eEqXze9UQWNixqsEcvKUcjYkvfnqf1JbYSdeljWwTg> <xmx:1WWgYq3Ygm8lc-meVDfYJV3HsGMkQ4jHhMwGjT_cu-C_q6lK8JNlug> Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 8 Jun 2022 05:03:16 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: Tomasz Duszynski <tduszynski@marvell.com> Cc: dev@dpdk.org, Jakub Palider <jpalider@marvell.com>, jerinj@marvell.com Subject: Re: [PATCH] raw/cnxk_gpio: allow controlling existing GPIO Date: Wed, 08 Jun 2022 11:03:15 +0200 Message-ID: <2104063.irdbgypaU6@thomas> In-Reply-To: <20220604140323.3380810-1-tduszynski@marvell.com> References: <20220604140323.3380810-1-tduszynski@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org 04/06/2022 16:03, Tomasz Duszynski: > Controlling existing GPIO should be normally frowned upon because > we want to avoid situation where multiple contenders modify GPIO > state simultaneously. > > Still there might be situations where this is actually needed. > Restarting killed application being an example here. > > So relax current restrictions and respect user needs. > > Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com> Applied, thanks.