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 15EF0C433FE for ; Wed, 26 Oct 2022 20:59:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234419AbiJZU7P (ORCPT ); Wed, 26 Oct 2022 16:59:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47048 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233706AbiJZU7P (ORCPT ); Wed, 26 Oct 2022 16:59:15 -0400 Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com [209.85.210.42]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F0FAD1217F6; Wed, 26 Oct 2022 13:59:13 -0700 (PDT) Received: by mail-ot1-f42.google.com with SMTP id 46-20020a9d0631000000b00666823da25fso3855132otn.0; Wed, 26 Oct 2022 13:59:13 -0700 (PDT) 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=9SGTpGJ14IzV3mTWmW98EDecB40xRhD+qIv4J7Ibrzc=; b=YPIlQzxmQNLVhT9Iq6roNrPwOMlfCCFpekAVKLwJyKZChoJhsHdqxBSa1TuTQV/V03 tBnfKKWFVmdTYHQybSESDQIK/srCKuxQyDEm+5a/cZWbM7mcNPTtBLo6FH3/2DrQxJEO p6AGoe0ZPw6uJfie4xbiVBGFDaKNMVLFkQOzn/tY2K0RLzoJSLRcev3glTVCb6uenCvu vV9YEeG71GqiMo12QuNppmGAz8T/TPxR3iBPuZtLyM8kPU4XLT0YzUrGaZQBqwp2YIqu KGEmQfJDvVU08ENHANqwMj3Puc75iQOOwbJbmrXTan/gROP50P12nCsaqKPEb6US6whS PYNQ== X-Gm-Message-State: ACrzQf3QrJQCGz5j1cplYkzgAKGa14WGRp6pB+dPcwoeL2M4fF0VBRaP gWqQP5t1umJ3XW8xHBvddA== X-Google-Smtp-Source: AMsMyM5kHygF1C7avKvdsYNEhsTiUfv1gpzHowhVZYUGRV2ZVyQ3RIJeLUWjNOlgHtBfx6JMZxuF2g== X-Received: by 2002:a05:6830:3987:b0:661:b516:6a61 with SMTP id bs7-20020a056830398700b00661b5166a61mr22873954otb.303.1666817953187; Wed, 26 Oct 2022 13:59:13 -0700 (PDT) Received: from robh_at_kernel.org (66-90-144-107.dyn.grandenetworks.net. [66.90.144.107]) by smtp.gmail.com with ESMTPSA id p1-20020a4a95c1000000b0047f72b6988fsm2563862ooi.45.2022.10.26.13.59.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 26 Oct 2022 13:59:12 -0700 (PDT) Received: (nullmailer pid 1303800 invoked by uid 1000); Wed, 26 Oct 2022 20:59:14 -0000 Date: Wed, 26 Oct 2022 15:59:14 -0500 From: Rob Herring To: Christoph Niedermaier Cc: linux-serial@vger.kernel.org, linux-arm-kernel@lists.infradead.org, krzysztof.kozlowski+dt@linaro.org, marex@denx.de, jirislaby@kernel.org, Greg Kroah-Hartman , devicetree@vger.kernel.org Subject: Re: [PATCH 1/4] dt_bindings: rs485: Add binding for GPIO that controls Rx enable during Tx Message-ID: <20221026205914.GA1294440-robh@kernel.org> References: <20221026165049.9541-1-cniedermaier@dh-electronics.com> <20221026165049.9541-2-cniedermaier@dh-electronics.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221026165049.9541-2-cniedermaier@dh-electronics.com> Precedence: bulk List-ID: X-Mailing-List: linux-serial@vger.kernel.org On Wed, Oct 26, 2022 at 06:50:46PM +0200, Christoph Niedermaier wrote: > Add the binding for a generic definition of a GPIO, that controls whether Rx > is connected or disconnected by an electrical circuit to have the ability > to receive the signals on the bus during sending or disable receiving during > sending. > > Signed-off-by: Christoph Niedermaier > --- > Cc: Greg Kroah-Hartman > Cc: Rob Herring > Cc: Krzysztof Kozlowski > Cc: Marek Vasut > Cc: devicetree@vger.kernel.org > To: linux-serial@vger.kernel.org > To: linux-arm-kernel@lists.infradead.org > --- > Documentation/devicetree/bindings/serial/rs485.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/serial/rs485.yaml b/Documentation/devicetree/bindings/serial/rs485.yaml > index 90a1bab40f05..0ebd7690f85d 100644 > --- a/Documentation/devicetree/bindings/serial/rs485.yaml > +++ b/Documentation/devicetree/bindings/serial/rs485.yaml > @@ -51,6 +51,10 @@ properties: > description: GPIO pin to enable RS485 bus termination. > maxItems: 1 > > + rs485-rx-during-tx-gpios: > + description: GPIO pin to control RS485 Rx enable during Tx. Active state means do what? And inactive? This is an output gating the RX signal or an input telling the receiver what to do during tx? The description is not adequate. How does this property relate to 'rs485-rx-during-tx' Any combination of the 2 being present or not is okay? If not, you need some constraints. Rob 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 57489C433FE for ; Wed, 26 Oct 2022 21:00:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Fuwr0Q85pkh9WrSpZdWE239xSA39atC/c3kRqaiA33c=; b=t9NvMW47gBiEP4 5LcAOQM+AvsUd6meajpTv+H1StDf2WmTArNda5jUOSLdh31lbdMMGgQiq/WoUxD2owS9WgrxDVjDm UCflR/+0YnBCsZrYvsaH+WIPQWiDS7MZSfy0+FTSnALOIXRr4uiV3tR6W8PoskXqA2lgfNopWkWSr BuAhicsSvSw/G4r61QzzXfWHB1vLjdlGbDsayLBAnXAm0kISUMmgrN4oxWbbWuyXdNhfbS6zE3wtR e7VQy1uR10BDS2cyAbpV/nE+JBCwGE86R5OcYN2sRpTMgXnHiHSKV3G3GML47XzTLePRxB3u8amyW yaMu1kFAkFPJd0lXMB6A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1onnUf-00AzAn-V3; Wed, 26 Oct 2022 20:59:22 +0000 Received: from mail-ot1-f50.google.com ([209.85.210.50]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1onnUc-00AzA0-RB for linux-arm-kernel@lists.infradead.org; Wed, 26 Oct 2022 20:59:20 +0000 Received: by mail-ot1-f50.google.com with SMTP id 16-20020a9d0490000000b0066938311495so2460919otm.4 for ; Wed, 26 Oct 2022 13:59:14 -0700 (PDT) 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=9SGTpGJ14IzV3mTWmW98EDecB40xRhD+qIv4J7Ibrzc=; b=G5tUdlSPJFGJefZLs0MqJPfa9GMZBSnjViXSq3ZoegEK22N4V8AXAi2bPOmij3Kcx1 bbYohVymHDLegSQYvdqKIBq2WMgklwfE+z02uOeu6XyzwujD93xo6jnm5SIYWH/oBufE TQSJWP9p4w+08x56FjzghQytCQp2+TqseWpqIAJ3gaVHDEK0Kvs3yb9gmAzFB4+5iH04 HguEmTfz3m4KrGqbFT9cNbjvbbGnWofYnqyda902Q4CG0sbmHbE8O5+gbXVk3qp5FUah KxcrApwQa9U+O25IM85J/lqPYBEtVzn03pG96gFHwzPdPVedO1RAUNjX11jJtSay2K6A hVWw== X-Gm-Message-State: ACrzQf2e9yiFsaUyzhZKKazF21rIPqJNUHRNs4iJYWUMrXQAmOLicLGh ogbk/w29WDARqdm8RRwWrUn539RNsg== X-Google-Smtp-Source: AMsMyM5kHygF1C7avKvdsYNEhsTiUfv1gpzHowhVZYUGRV2ZVyQ3RIJeLUWjNOlgHtBfx6JMZxuF2g== X-Received: by 2002:a05:6830:3987:b0:661:b516:6a61 with SMTP id bs7-20020a056830398700b00661b5166a61mr22873954otb.303.1666817953187; Wed, 26 Oct 2022 13:59:13 -0700 (PDT) Received: from robh_at_kernel.org (66-90-144-107.dyn.grandenetworks.net. [66.90.144.107]) by smtp.gmail.com with ESMTPSA id p1-20020a4a95c1000000b0047f72b6988fsm2563862ooi.45.2022.10.26.13.59.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 26 Oct 2022 13:59:12 -0700 (PDT) Received: (nullmailer pid 1303800 invoked by uid 1000); Wed, 26 Oct 2022 20:59:14 -0000 Date: Wed, 26 Oct 2022 15:59:14 -0500 From: Rob Herring To: Christoph Niedermaier Cc: linux-serial@vger.kernel.org, linux-arm-kernel@lists.infradead.org, krzysztof.kozlowski+dt@linaro.org, marex@denx.de, jirislaby@kernel.org, Greg Kroah-Hartman , devicetree@vger.kernel.org Subject: Re: [PATCH 1/4] dt_bindings: rs485: Add binding for GPIO that controls Rx enable during Tx Message-ID: <20221026205914.GA1294440-robh@kernel.org> References: <20221026165049.9541-1-cniedermaier@dh-electronics.com> <20221026165049.9541-2-cniedermaier@dh-electronics.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20221026165049.9541-2-cniedermaier@dh-electronics.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221026_135918_900083_4CCAFCD7 X-CRM114-Status: GOOD ( 19.64 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Oct 26, 2022 at 06:50:46PM +0200, Christoph Niedermaier wrote: > Add the binding for a generic definition of a GPIO, that controls whether Rx > is connected or disconnected by an electrical circuit to have the ability > to receive the signals on the bus during sending or disable receiving during > sending. > > Signed-off-by: Christoph Niedermaier > --- > Cc: Greg Kroah-Hartman > Cc: Rob Herring > Cc: Krzysztof Kozlowski > Cc: Marek Vasut > Cc: devicetree@vger.kernel.org > To: linux-serial@vger.kernel.org > To: linux-arm-kernel@lists.infradead.org > --- > Documentation/devicetree/bindings/serial/rs485.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/serial/rs485.yaml b/Documentation/devicetree/bindings/serial/rs485.yaml > index 90a1bab40f05..0ebd7690f85d 100644 > --- a/Documentation/devicetree/bindings/serial/rs485.yaml > +++ b/Documentation/devicetree/bindings/serial/rs485.yaml > @@ -51,6 +51,10 @@ properties: > description: GPIO pin to enable RS485 bus termination. > maxItems: 1 > > + rs485-rx-during-tx-gpios: > + description: GPIO pin to control RS485 Rx enable during Tx. Active state means do what? And inactive? This is an output gating the RX signal or an input telling the receiver what to do during tx? The description is not adequate. How does this property relate to 'rs485-rx-during-tx' Any combination of the 2 being present or not is okay? If not, you need some constraints. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel