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 10A08C4332F for ; Wed, 12 Oct 2022 18:51:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229625AbiJLSu7 (ORCPT ); Wed, 12 Oct 2022 14:50:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57512 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229932AbiJLSu6 (ORCPT ); Wed, 12 Oct 2022 14:50:58 -0400 Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D98AEE070C for ; Wed, 12 Oct 2022 11:50:53 -0700 (PDT) Received: by mail-wr1-x42e.google.com with SMTP id bu30so27512376wrb.8 for ; Wed, 12 Oct 2022 11:50:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=iQhlZRnJ0m4X2vc4+2LyXOMiawQABMxJ/mhVJlXpyFg=; b=xMNjvf+iP47KsXXvWRx0u3fSGwg+++0J4Fte26zqd3QXweAzJju6VUxhJ1ncoFer3c hdU6ZC2WmqVvyYCdZp+mOpqsallTsYpcTVbfTQFQOS/TboZ5uPi2kS6rhiUbtgYx8vB3 MRJ1SpNH4IewAGwM8G/NifGm+kufLzutUHEFoRggbVmFdJGwROdqLdIV4L+1wbHlqj4R 3wI/1RjABzR+HSCzU/xl3lwEm8xjPPsw5IPHLR2mZiZp05hLNVOi/tXnMf9guAVQyyIU MeIRe9HUG3bMm2JhRMXi2v1NL0mjlX39lbFS1iH469C4CQhF1vVfUe1s6z1qRbuKxn8i aRMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=iQhlZRnJ0m4X2vc4+2LyXOMiawQABMxJ/mhVJlXpyFg=; b=DzrGnzHK/udtQht9uxmo92j6WklF3Kr7SoOoCgnlfTtF1GbFGi9zypSl0QwzfcFu3X bzWs6s+GSFcQMQ2bsJy/0KtdPZ8qrZT+TkmYjeDNWJNoG1x4mOyh6s9phSkT3Wps70q0 yitWbDEv0FsWkWADDnU3vREG/whDB5ZI9KhUOi19W4olTWU1xoi7bGMUhms3BOY004gt UI8vnXUF/E4P0Oc0fnJo0bsaev7sFwPU+qW8rEs0Gwf2Xn41ru70J/Nf7OOiusysrzZf NKot1Os6zzGKIAM7h3+3OMzZPnZnzY85MISNvQHBISN/urCE6WCKMMXW8cvyyeSLpPuB sCFg== X-Gm-Message-State: ACrzQf0r2CR/jEFJFSrPrsLdlQuuPGpcB3oN1c+vkGoVLWXT0WdhYx0e WTyLfkG0xfnmvaObpE5HvP7ecw== X-Google-Smtp-Source: AMsMyM7kipgPbjIt6m4K8/GYYZTCjos7DxuGJh1RnAl0Ye38UQ60uXZy6uGh5XzIscj6pI9IK+JR6g== X-Received: by 2002:a5d:6701:0:b0:22e:6545:995d with SMTP id o1-20020a5d6701000000b0022e6545995dmr18944278wru.301.1665600652184; Wed, 12 Oct 2022 11:50:52 -0700 (PDT) Received: from maple.lan (cpc141216-aztw34-2-0-cust174.18-1.cable.virginm.net. [80.7.220.175]) by smtp.gmail.com with ESMTPSA id s14-20020adfecce000000b0022e653f5abbsm332083wro.69.2022.10.12.11.50.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 12 Oct 2022 11:50:51 -0700 (PDT) Date: Wed, 12 Oct 2022 19:50:49 +0100 From: Daniel Thompson To: Dmitry Torokhov Cc: Linus Walleij , Bartosz Golaszewski , linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org, Andy Shevchenko , linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org Subject: Re: [PATCH 4/7] gpiolib: of: add a quirk for reset line for Marvell NFC controller Message-ID: References: <20221011-gpiolib-quirks-v1-0-e01d9d3e7b29@gmail.com> <20221011-gpiolib-quirks-v1-4-e01d9d3e7b29@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Wed, Oct 12, 2022 at 11:45:02AM -0700, Dmitry Torokhov wrote: > On Wed, Oct 12, 2022 at 11:29:02AM +0100, Daniel Thompson wrote: > > On Tue, Oct 11, 2022 at 03:19:32PM -0700, Dmitry Torokhov wrote: > > > The controller is using non-standard "reset-n-io" name for its reset > > > gpio property, whereas gpiod API expects "-gpios". Add a quirk > > > so that gpiod API will still work on unmodified DTSes. > > > > > > Signed-off-by: Dmitry Torokhov > > > > How/when has/will the DT bindings documentation for this hardware be > > updated to describe the new bindings? > > > > Delivering the quirks ahead of driver updates is great for avoiding > > merge conflicts but it also conceals the rename from reviewers so > > risks neglecting to update the bindings. > > I was planning on sending binding updates once driver patches land. I'd have a (weak) preference for them being shared in the same patchset. Maintainers can either ack or the changes can land seperately but having them in the same patchset helps avoid having to quibble or check! Daniel.