linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ikjoon Jang <ikjn@chromium.org>
To: linux-input@vger.kernel.org, devicetree@vger.kernel.org
Cc: Hsin-Yi Wang <hsinyi@chromium.org>,
	Dmitry Torokhov <dtor@chromium.org>,
	Nicolas Boichat <drinkcat@chromium.org>,
	Ikjoon Jang <ikjn@chromium.org>,
	Benson Leung <bleung@chromium.org>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Guenter Roeck <groeck@chromium.org>,
	Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v4 1/2] mfd: google,cros-ec: add DT bindings for a baseboard's switch device
Date: Mon, 12 Apr 2021 19:30:19 +0800	[thread overview]
Message-ID: <20210412113020.2724134-2-ikjn@chromium.org> (raw)
In-Reply-To: <20210412113020.2724134-1-ikjn@chromium.org>

This is for ChromeOS tablets which have a 'cros_cbas' switch device
in the "Whiskers" base board. This device can be instantiated only by
device tree on ARM platforms. ChromeOS EC doesn't provide a way to
probe the device.

Signed-off-by: Ikjoon Jang <ikjn@chromium.org>

---

Changes in v4:
Define cros-cbase bindings inside google,cros-ec.yaml instead of
a seperated binding document.

 .../devicetree/bindings/mfd/google,cros-ec.yaml  | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
index 76bf16ee27ec..c76809cd9f7f 100644
--- a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
+++ b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
@@ -127,6 +127,18 @@ patternProperties:
     type: object
     $ref: "/schemas/extcon/extcon-usbc-cros-ec.yaml#"
 
+  "^cbas$":
+    type: object
+    properties:
+      compatible:
+        const: google,cros-cbas
+    required:
+      - compatible
+    additionalProperties: false
+    description:
+      This device is used to signal when a detachable base is attached
+      to a Chrome OS tablet.
+
 required:
   - compatible
 
@@ -180,6 +192,10 @@ examples:
             interrupts = <99 0>;
             interrupt-parent = <&gpio7>;
             spi-max-frequency = <5000000>;
+
+            base_detection: cbas {
+                compatible = "google,cros-cbas";
+            };
         };
     };
 
-- 
2.31.1.295.g9ea45b61b8-goog


  reply	other threads:[~2021-04-12 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 11:30 [PATCH v4 0/2] HID: google: add device tree bindings for Whiskers switch device Ikjoon Jang
2021-04-12 11:30 ` Ikjoon Jang [this message]
2021-04-13 14:57   ` [PATCH v4 1/2] mfd: google,cros-ec: add DT bindings for a baseboard's " Rob Herring
2021-04-14  4:15     ` Ikjoon Jang
2021-04-12 11:30 ` [PATCH v4 2/2] HID: google: Add of_match table to Whiskers " Ikjoon Jang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210412113020.2724134-2-ikjn@chromium.org \
    --to=ikjn@chromium.org \
    --cc=bleung@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=dtor@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=hsinyi@chromium.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).