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=-8.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham 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 96FF4C43331 for ; Mon, 30 Mar 2020 19:11:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 69FF220748 for ; Mon, 30 Mar 2020 19:11:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1585595504; bh=4k7npMR5i0GlS48xwHDyMNHtVDzt8QFmx7L+bpSa+l8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=2b/adV5hK46M+mq+I6np6WGqh5i0PbmEa+SF7OoGO6qoseXlAvDPodcbv38RQ6wCV MQqzTtg2l5UV5O+IqABEqfaG5Yi+CV3lYuppsH8axnXniH1LR06TmXC889y3o0SzR4 /7W4fiIcgKa/VYl6uw/CRVDTuKsePxGhSRPzwEEw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728230AbgC3TLn (ORCPT ); Mon, 30 Mar 2020 15:11:43 -0400 Received: from mail-io1-f68.google.com ([209.85.166.68]:41878 "EHLO mail-io1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726672AbgC3TLl (ORCPT ); Mon, 30 Mar 2020 15:11:41 -0400 Received: by mail-io1-f68.google.com with SMTP id b12so2820877ion.8; Mon, 30 Mar 2020 12:11:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=naEzHVNq1KsTafl3xqH4koGPBy3a41PHj0Hsijlhu9s=; b=V9XgwZMdMFb5UgUDyekxjidiupCOGMZ3G+RcgpWzgcqjrzIbE29RiQQwIVIx3kfOSH MuESVCaxjKFSdA4i4BAkMr9S87yNfZHf4+88rOg3S4QU9Onm4CsP5lOer6CB2CpnYcQN e5xCj9YXkQLqHJvSMqluWnJaBEnYoIJE9Pt6bhSWLGhVJaKnBIp9+dCcZRhKQLaV7uCF mwPpbSDCqw0WpF8F9Su6+UOXTy8FI02MXbSZsQ2SOrAJI3+tzS64nBcuZCdS6o8W7sMn zGB12rg+FIcmVOT8ubNboZPHMmfnaIBa4Qba5H2kOmFjtv02qjwuunxcGHa9uFQjjgUE feiA== X-Gm-Message-State: ANhLgQ1HWaSk8NwcKXctBCl0DTzJjGpxocObElUSFnL2A0HRc4+qW91T opkoiVsDpgHx3W9I98h2KQ== X-Google-Smtp-Source: ADFU+vsYIatZ1bjntaO5hjkGBwkqDPSOhoxi4SXRJcj+KJOdK7tBb4Gb0GLh/lVqM6oByQICfnINPw== X-Received: by 2002:a6b:8dc9:: with SMTP id p192mr11427400iod.90.1585595498899; Mon, 30 Mar 2020 12:11:38 -0700 (PDT) Received: from rob-hp-laptop ([64.188.179.250]) by smtp.gmail.com with ESMTPSA id v80sm5125001ila.62.2020.03.30.12.11.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 30 Mar 2020 12:11:37 -0700 (PDT) Received: (nullmailer pid 6109 invoked by uid 1000); Mon, 30 Mar 2020 19:11:35 -0000 Date: Mon, 30 Mar 2020 13:11:35 -0600 From: Rob Herring To: Paul Cercueil Cc: Nick Dyer , Dmitry Torokhov , Mark Rutland , linux-input@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] dt-bindings: input: Update atmel,maxtouch.txt to YAML Message-ID: <20200330191135.GA22010@bogus> References: <20200315100416.14151-1-paul@crapouillou.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200315100416.14151-1-paul@crapouillou.net> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Mar 15, 2020 at 11:04:15AM +0100, Paul Cercueil wrote: > Update atmel,maxtouch.txt to YAML. The new 'vdd-supply' property was > added in the process. > > Signed-off-by: Paul Cercueil > --- > .../bindings/input/atmel,maxtouch.txt | 41 ----------- > .../bindings/input/atmel,maxtouch.yaml | 68 +++++++++++++++++++ > 2 files changed, 68 insertions(+), 41 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/input/atmel,maxtouch.txt > create mode 100644 Documentation/devicetree/bindings/input/atmel,maxtouch.yaml > > diff --git a/Documentation/devicetree/bindings/input/atmel,maxtouch.txt b/Documentation/devicetree/bindings/input/atmel,maxtouch.txt > deleted file mode 100644 > index c88919480d37..000000000000 > --- a/Documentation/devicetree/bindings/input/atmel,maxtouch.txt > +++ /dev/null > @@ -1,41 +0,0 @@ > -Atmel maXTouch touchscreen/touchpad > - > -Required properties: > -- compatible: > - atmel,maxtouch > - > - The following compatibles have been used in various products but are > - deprecated: > - atmel,qt602240_ts > - atmel,atmel_mxt_ts > - atmel,atmel_mxt_tp > - atmel,mXT224 > - > -- reg: The I2C address of the device > - > -- interrupts: The sink for the touchpad's IRQ output > - See ../interrupt-controller/interrupts.txt > - > -Optional properties for main touchpad device: > - > -- linux,gpio-keymap: When enabled, the SPT_GPIOPWN_T19 object sends messages > - on GPIO bit changes. An array of up to 8 entries can be provided > - indicating the Linux keycode mapped to each bit of the status byte, > - starting at the LSB. Linux keycodes are defined in > - . > - > - Note: the numbering of the GPIOs and the bit they start at varies between > - maXTouch devices. You must either refer to the documentation, or > - experiment to determine which bit corresponds to which input. Use > - KEY_RESERVED for unused padding values. > - > -- reset-gpios: GPIO specifier for the touchscreen's reset pin (active low) > - > -Example: > - > - touch@4b { > - compatible = "atmel,maxtouch"; > - reg = <0x4b>; > - interrupt-parent = <&gpio>; > - interrupts = ; > - }; > diff --git a/Documentation/devicetree/bindings/input/atmel,maxtouch.yaml b/Documentation/devicetree/bindings/input/atmel,maxtouch.yaml > new file mode 100644 > index 000000000000..1b138a9836bf > --- /dev/null > +++ b/Documentation/devicetree/bindings/input/atmel,maxtouch.yaml > @@ -0,0 +1,68 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) Do you have rights to relicense? > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/input/atmel,maxtouch.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Atmel maXTouch touchscreen/touchpad DT bindings > + > +maintainers: > + - Paul Cercueil > + > +properties: > + compatible: > + enum: > + - atmel,maxtouch > + > + reg: > + maxItems: 1 > + > + interrupts: > + maxItems: 1 > + > + vdd-supply: > + description: Phandle to regulator providing power to the touchscreen > + > + linux,gpio-keymap: > + minItems: 1 > + maxItems: 8 Needs a type reference (uint32-array). > + description: > > + When enabled, the SPT_GPIOPWN_T19 object sends messages > + on GPIO bit changes. An array of up to 8 entries can be provided > + indicating the Linux keycode mapped to each bit of the status byte, > + starting at the LSB. Linux keycodes are defined in > + . > + > + Note: the numbering of the GPIOs and the bit they start at varies between > + maXTouch devices. You must either refer to the documentation, or > + experiment to determine which bit corresponds to which input. Use > + KEY_RESERVED for unused padding values. > + > + reset-gpios: > + description: GPIO specifier for the touchscreen's reset pin (active low) maxItems: 1 > + > +required: > + - compatible > + - reg > + - interrupts > + > +additionalProperties: false > + > +examples: > + - | > + #include > + > + i2c { > + #address-cells = <1>; > + #size-cells = <0>; > + > + mxt224-touchscreen@4a { touchscreen@4a > + compatible = "atmel,maxtouch"; > + reg = <0x4a>; > + > + interrupt-parent = <&gpx0>; > + interrupts = <4 IRQ_TYPE_EDGE_FALLING>; > + > + vdd-supply = <&tsp_reg>; > + }; > + }; > -- > 2.25.1 >