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=-6.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 72365CA9EC2 for ; Tue, 29 Oct 2019 07:23:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4600E2086A for ; Tue, 29 Oct 2019 07:23:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="eMchEOvQ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729385AbfJ2HXT (ORCPT ); Tue, 29 Oct 2019 03:23:19 -0400 Received: from mail-ua1-f68.google.com ([209.85.222.68]:36121 "EHLO mail-ua1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387670AbfJ2HXE (ORCPT ); Tue, 29 Oct 2019 03:23:04 -0400 Received: by mail-ua1-f68.google.com with SMTP id f21so3192012uan.3 for ; Tue, 29 Oct 2019 00:23:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0SUH6/NtBC3ilVCpdONozL4mS3Prp0pIL3y1hHCcxAk=; b=eMchEOvQ/jKSqC7IlUVOrUOu2sRq3JlNHSwrSwCVZV7hyYX+NwsA3oadySVIS2GMhv Fvs0xOAQNNajFRHYthK70jYXsoHFLR0MqpOCX4UruR1XUSVhwPotDPQQJvLDpR6Qs35N fO+lH1wwkAdlVyFMk0fkQlRl+r7cTgEooYDbw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0SUH6/NtBC3ilVCpdONozL4mS3Prp0pIL3y1hHCcxAk=; b=FvrCwGacAnqLVQvraznTvPJd18Wo2/kP3vIac2V6sFlOfuyp8BYOOL4vBO4NoIlGJH Bbc+RizlTnr576BUW6zDT4h5ehAPgBcpZPPWmydtpgyovapz4QIJdlmCPbxOQohfjow3 f+D5GD9NwOHaGoi7Pw01IPF7SIaSBorL+OwdYj99+53jiaJLtxEQF4ld3WBFPyDnKEsJ UNGsrk6DkRqW5nBRdGAZGsUWp3oayYke7+8UVWcUpAfHjAGSLZqiBO/NNrbwqOeI/yVr 8EO3l1IxyH/FryQoHKuMxARLdsDgHvRlJQzLruSsgrbt0TGNoA94DTnCAhzdvLhvJ1/b GoYA== X-Gm-Message-State: APjAAAWayI0jdXz7GDK4EDs6h/Z84bPAaVQwGfGfpsTlJodcr1SgDmww VMo2z8qid/Fnhb9p53i4n3Pkldgg3KKpcKjELi9TCqUDg4A= X-Google-Smtp-Source: APXvYqwu6KYbConXB0iKr6Mov1RGaa3I/esweFtuANMt32BxSyqi5DbWOfQ88/Vd4VamORlLwO9ez57AWW6x/2gTwcw= X-Received: by 2002:ab0:6503:: with SMTP id w3mr7651016uam.17.1572333783797; Tue, 29 Oct 2019 00:23:03 -0700 (PDT) MIME-Version: 1.0 References: <20191023024348.225969-1-ikjn@chromium.org> <20191025194101.GA4734@bogus> In-Reply-To: <20191025194101.GA4734@bogus> From: Ikjoon Jang Date: Tue, 29 Oct 2019 15:22:52 +0800 Message-ID: Subject: Re: [PATCH v3 1/2] dt-bindings: input: Add DT bindings for Whiskers switch To: Rob Herring Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org, Dmitry Torokhov , Mark Rutland , Jiri Kosina , Benjamin Tissoires , linux-kernel@vger.kernel.org, Nicolas Boitchat Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 26, 2019 at 3:41 AM Rob Herring wrote: > > On Wed, Oct 23, 2019 at 10:43:48AM +0800, Ikjoon Jang wrote: > > Add the DT binding document for Hammer's TABLET_MODE switch. > > This doesn't have any properties. Why does it need to be in DT? Just > have the EC driver instantiate it. > > > > > Signed-off-by: Ikjoon Jang > > --- > > .../devicetree/bindings/input/cros-cbas.yaml | 22 +++++++++++++++++++ > > 1 file changed, 22 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/input/cros-cbas.yaml > > > > diff --git a/Documentation/devicetree/bindings/input/cros-cbas.yaml b/Documentation/devicetree/bindings/input/cros-cbas.yaml > > new file mode 100644 > > index 000000000000..3bc989c6a295 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/input/cros-cbas.yaml > > @@ -0,0 +1,22 @@ > > +# SPDX-License-Identifier: GPL-2.0 > > (GPL-2.0-only OR BSD-2-Clause) for new bindings please. This will be GPL-2.0-only in next patch. > > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/input/cros-cbas.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: ChromeOS Hammer's Base Attached Switch > > + > > +maintainers: > > + - Dmitry Torokhov > > + > > +description: > > + This device is used to signal when a detachable base is attached to a > > + Chrome OS tablet. The node for this device must be under a cros-ec node > > + like google,cros-ec-spi or google,cros-ec-i2c. > > This should probably just be part of an EC schema where it can be > enforced that this is a child node. It could be either embedded into it > or referenced. I'd lean toward the former given this is only a > compatible string... Sorry for basic questions here but I'm a bit confused, "embedding" means that cros-ec.txt should be converted into json schema first and embed this child bindings into there? Many Chrome OS tablets have a switch exposed by 'cros-ec-keyb' device which is directly controlled by EC. But this 'cros_cbas' switch device is for other types of tablets which need additional logics on EC and HID. Currently it doesn't need to have other properties, but maybe it could require additional properties or device links in the future, plus this device is not just a EC subdevice, so I'd prefer this to be a separate binding. > > > + > > +properties: > > + compatible: > > + const: google,cros-cbas > > + > > +required: > > + - compatible > > Add here: > > additionalProperties: false. Okay, I will add this in a new patch set , thank you! > > > -- > > 2.23.0.866.gb869b98d4c-goog > >