Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2247303imu; Sat, 8 Dec 2018 19:11:26 -0800 (PST) X-Google-Smtp-Source: AFSGD/X8+R6UEk9K57IyBSJtDCLwwKoRgOxec+YMuLDtwJzwkJT++BxQRZhedqIJgNsVyqN5t4+o X-Received: by 2002:a63:1444:: with SMTP id 4mr6870958pgu.430.1544325086475; Sat, 08 Dec 2018 19:11:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544325086; cv=none; d=google.com; s=arc-20160816; b=uW1F7P/K2kmyyLF1u+vw9sT0JbV8YSDSjXE/KZdrslY5TKCQ6sxSTpVuRoVaa4LjXt emA2fpJh3Z+MlbRm+7BdNquae1UF+GukvIho+rO8H4kxvvo+oJlKTSwYUOEaBYBj+sPp jC0Y4LAGdx6Zix/U8ODSIl0ornnWKT3h2lVmE84LJHPFk2uk/p1RYCpLp1w5fmJAKF1E /ST1Rv1SVw/Awmk3DxIQRMgaKj+jjs0hS0dGTLxD5/7lU9A3r0DUnns4WXX4MYqAGDB0 qAmHj6Gs67AS8SxMdEGPj02tAnBbZrhweac1nyiDuihN+HoeEIEuIkEMpSW1yBY6gASu KTng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-transfer-encoding :content-disposition:mime-version:in-reply-to:references:subject:cc :to:from:date:message-id; bh=D4zvXEtwZVetzHqNPyelttLuIbtzmJfQwqND7YKq5JU=; b=HhR/aac0J13J/4XUsfbMYbkNhGx9zkDnDmV1G1yo9NOk7ZcCfuI9HAAOeLvDcsL5T/ NJ7mM2F1ZwrqA6li+OGiRcQvih702l7m7bYGgaPmsHDn3ol4Ocy+1oEJt5BRRIQJCXw+ Goo/SIkbMmE+oBII9DcT8LZJQ2hlzAmWB0t1UDfStBhPtJM2bW9S3LoDaB30Rp5whAOs WU1DKmqk/jhz1H2U2mQ044lf7pPsii6OPRJ959a7WlENsuJms7HstLlIW3VEqBc2wk9Y Nifq6i539aavTYUahjm42UTRqsqiwv5EqoIxzb28PhYUWlM/YzLbZA20C1WDEcAwTJpm B/EA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=aussec.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p5si5655670pls.338.2018.12.08.19.10.27; Sat, 08 Dec 2018 19:11:26 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=aussec.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726067AbeLIDIZ (ORCPT + 99 others); Sat, 8 Dec 2018 22:08:25 -0500 Received: from csm1.csm-office.com.au ([165.228.118.109]:40860 "EHLO sleepy.aussec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725947AbeLIDIZ (ORCPT ); Sat, 8 Dec 2018 22:08:25 -0500 X-Virus-Scanned: amavisd-new at aussec.com Received: from sneezy.aussec.com (sneezy.aussec.com [172.16.0.4]) by sleepy.aussec.com (8.15.2/8.15.2) with ESMTP id wB9384dX012814; Sun, 9 Dec 2018 14:08:09 +1100 Received: from 1.128.104.17 ([1.128.104.17]) by www.aussec.com (Horde Framework) with HTTP; Sun, 09 Dec 2018 14:07:59 +1100 Message-ID: <20181209140759.18342zz66oeo3767@www.aussec.com> Date: Sun, 09 Dec 2018 14:07:59 +1100 From: tom burkart To: Rob Herring Cc: "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org, lukas@fridolin.com Subject: Re: [PATCH v9 3/4] dt-bindings: pps: pps-gpio PPS ECHO implementation References: <20181122094602.5156-1-tom@aussec.com> <20181122094602.5156-2-tom@aussec.com> <20181122094602.5156-3-tom@aussec.com> <20181122094602.5156-4-tom@aussec.com> <20181127150629.10795h1esqtc53ut@aussec.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Rob Herring : > On Mon, Nov 26, 2018 at 10:06 PM tom burkart wrote: >> >> Hi Rob, >> >> Quoting Rob Herring : >> >> > On Thu, Nov 22, 2018 at 3:49 AM Tom Burkart wrote: >> >> >> >> This patch implements the device tree changes required for the pps >> >> echo functionality for pps-gpio, that sysfs claims is available >> >> already. >> >> >> >> This patch was originally written by Lukas Senger as part of a masters >> >> thesis project and modified for inclusion into the linux kernel by Tom >> >> Burkart. >> >> >> >> Signed-off-by: Lukas Senger >> >> Signed-off-by: Tom Burkart >> >> --- >> >> Documentation/devicetree/bindings/pps/pps-gpio.txt | 9 +++++++++ >> >> 1 file changed, 9 insertions(+) >> >> >> >> diff --git a/Documentation/devicetree/bindings/pps/pps-gpio.txt >> >> b/Documentation/devicetree/bindings/pps/pps-gpio.txt >> >> index 1155d49c2699..e09f6f2405c5 100644 >> >> --- a/Documentation/devicetree/bindings/pps/pps-gpio.txt >> >> +++ b/Documentation/devicetree/bindings/pps/pps-gpio.txt >> >> @@ -7,10 +7,15 @@ Required properties: >> >> - compatible: should be "pps-gpio" >> >> - gpios: one PPS GPIO in the format described by ../gpio/gpio.txt >> >> >> >> +Additional required properties for the PPS ECHO functionality: >> >> +- echo-gpios: one PPS ECHO GPIO in the format described by >> ../gpio/gpio.txt >> >> +- echo-active-ms: duration in ms of the active portion of the echo pulse >> >> + >> >> Optional properties: >> >> - assert-falling-edge: when present, assert is indicated by a >> falling edge >> >> (instead of by a rising edge) >> >> - capture-clear: when present, also capture the PPS clear event >> >> +- invert-pps-echo: when present, invert the PPS ECHO pulse >> > >> > Why do you need this? Can't you just make the echo gpio GPIO_ACTIVE_LOW? >> > >> > BTW, using the flag probably should have been done for >> > 'assert-falling-edge' as well. >> >> The hardware I use expects a positive-going echo pulse, however, it >> was really easy to give users the option to have it inverted in case >> they use different hardware that expects a negative-going edge. > > It will be even easier to implement if you use GPIO_ACTIVE_LOW or > GPIO_ACTIVE_HIGH as appropriate. If the flag is set appropriately, > then gpiod_set_value(gpio, 1) asserts the pulse and > gpiod_set_value(gpio, 0) deasserts it no matter which way the h/w is > wired. You can then get rid of invert_pps_echo in the driver. Hi Rob, sure we can do that, however, a hardware change will need a recompile of the kernel, rather than setting a flag. You still need something to help decide whether to use GPIO_ACTIVE_LOW or GPIO_ACTIVE_HIGH depending on what hardware is currently connected to the system. I am happy to delete that code as well, if it makes you happy. Tom