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 X-Spam-Level: X-Spam-Status: No, score=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9F3CBC47096 for ; Thu, 3 Jun 2021 10:03:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 883CB611CA for ; Thu, 3 Jun 2021 10:03:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229941AbhFCKFU (ORCPT ); Thu, 3 Jun 2021 06:05:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41794 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229894AbhFCKFT (ORCPT ); Thu, 3 Jun 2021 06:05:19 -0400 Received: from polaris.svanheule.net (polaris.svanheule.net [IPv6:2a00:c98:2060:a004:1::200]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6475DC06174A for ; Thu, 3 Jun 2021 03:03:35 -0700 (PDT) Received: from [IPv6:2a02:a03f:eafb:ee01:398f:956e:2c86:f184] (unknown [IPv6:2a02:a03f:eafb:ee01:398f:956e:2c86:f184]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: sander@svanheule.net) by polaris.svanheule.net (Postfix) with ESMTPSA id 2A60220804A; Thu, 3 Jun 2021 12:03:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=svanheule.net; s=mail1707; t=1622714613; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+jqxeeHE2pvKOfNp3PIxGrAXlH3QpY7gaOLQeOxcS/s=; b=NqLeydT59bSTvV8Z8ogmgK2XCDNONLd9qe6tcdCdXHx+RSLTQSHHDXug0biMruR2LybETn 7V6O19Mw0ZHjIxU4ilgparRmeb1mCTurClnmL+CegwSH3Qc97os5H3pqCyXfJZE8iMohUF gHFQSCH08N+seNqXDfgwWO48etDl/9McPD90eo+Mxqkc+z2etzHcwPjhIHD+kiyG3q5z2r v1zTq0H92QbNgCVyyZyE5X8CdQaEi3JARVjkyz9lBIpOcrp+6og5ET/8XlnRWzsXxZI3w7 gzR3cOWT/kcipAKSeoMGn2nDq8NpwKM6NCL6+8pYi9kupMJdQslyATZ7uBvQyQ== Message-ID: Subject: Re: [PATCH v3 1/6] gpio: regmap: Add quirk for output data register From: Sander Vanheule To: Michael Walle , Bartosz Golaszewski Cc: Pavel Machek , Rob Herring , Lee Jones , Mark Brown , Greg Kroah-Hartman , "Rafael J . Wysocki" , Linus Walleij , linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-gpio@vger.kernel.org, Andrew Lunn , Andy Shevchenko , linux-kernel@vger.kernel.org Date: Thu, 03 Jun 2021 12:03:31 +0200 In-Reply-To: <001c48fb08887cbec88f79ebe3bf644b@walle.cc> References: <001c48fb08887cbec88f79ebe3bf644b@walle.cc> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Michael, Bartosz, On Fri, 2021-05-28 at 08:40 +0200, Michael Walle wrote: > Am 2021-05-24 00:33, schrieb Sander Vanheule: > > GPIO chips may not support setting the output value when a pin is > > configured as an input, although the current implementation assumes > > this > > is always possible. > > > > Add support for setting pin direction before value. The order defaults > > to setting the value first, but this can be reversed by setting the > > GPIO_REGMAP_QUIRK_SET_DIRECTION_FIRST flag in regmap_config.quirks. > > Nice! If this is really needed: > > Reviewed-by: Michael Walle Looks like the quirk won't be needed for this series, but I can always resubmit it separately if needed. Best, Sander