Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp3607382rwl; Tue, 27 Dec 2022 11:52:00 -0800 (PST) X-Google-Smtp-Source: AMrXdXvMpC/G8/rc81+R/aUVk65fu0xz8zNa9k0uGcL3rmK7Xt6jOv2Axa/7O1jNZ9qcxY2gNK4i X-Received: by 2002:a05:6a20:4faa:b0:ad:efca:25c1 with SMTP id gh42-20020a056a204faa00b000adefca25c1mr41501705pzb.14.1672170720755; Tue, 27 Dec 2022 11:52:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672170720; cv=none; d=google.com; s=arc-20160816; b=en1J5SXRISEPI12KNFQqTnw709evKOLG2iV1lfftZQ4NAEEu+uvR5vxXr8X+Ff7HQV RkkwiDq5mmDxqzqMFmOhr3UHkTSs6FXsLrI6Bq/hajXFKh1tBdGZpueuTOLn7muwpU4N e8tNTqbHMn9JeRQ9loh/nTkkvIQGP9RHIOm/4HX+AyuMDEwQpT2+MLFTIU+yFhAxrnJ+ I7jNyZ6EjRsV2RdZCyZmfhBzyt2DiSXjyPQV2py4jbteL2q8ISZmAPYc7i6O0E2uQ03b NccO4woBEo9oLGw06Sh7R9JsaUTOcl4Fj9jEXNXsQX29KG8aYINPn6j3wWsUXW36gcx3 QV8A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=1NE5d0lxAdxXOL2nWwxUeL+Wf2ItY+N8jvCklovTdI8=; b=pUVvvCZUv5TqCUwiN+X/hw3+G1YEJzoFYR+iNBsByj/U0BrUhSCjOtOVS3Mk4IKzwj BvbodQu9tlrDcmy0Hc6N/yfR/TYPQjC0qJRyGn/0ZWUEw+xycctAOGLXEEuBv121/B8D c8RVynm5NfJ5rR3ig4z6Ieqa7Jn8+k9BItW9rtAvpXax653dYwUr3aOu/unahRufzbaw sgl73Po/sAKzpfpCv/L9lFpzDXHQbkbfMtZlLoOuCMZe8plNKYJhJfMMrL6t24W/n+wV dGd3uEXvdHEg2gUBGIzuE1MdYi1WbkgnBp3C2BAlyYyxcph8ADRBKVkImppeSe5GxIzt YnmQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=ZU7hVaxl; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b7-20020a656687000000b00496bc7b662csi12262763pgw.637.2022.12.27.11.51.51; Tue, 27 Dec 2022 11:52:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=ZU7hVaxl; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231521AbiL0TdS (ORCPT + 66 others); Tue, 27 Dec 2022 14:33:18 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50554 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230454AbiL0TdH (ORCPT ); Tue, 27 Dec 2022 14:33:07 -0500 Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 32FC3D2C5 for ; Tue, 27 Dec 2022 11:33:06 -0800 (PST) Received: by mail-io1-xd2b.google.com with SMTP id d123so7330326iof.6 for ; Tue, 27 Dec 2022 11:33:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=1NE5d0lxAdxXOL2nWwxUeL+Wf2ItY+N8jvCklovTdI8=; b=ZU7hVaxlc2Z6/FY0OVxnYgSn1236LzQmO45sPj4Rnz6qGZuzu6mf76ojheaMgApR3S A+keFrT6ujnMgVXrk85N3uZiQHVmkALI7AuOk8ixSsibcZRcR66BGH76Pc7gB++UbezD +xmhXK1Ol5kHxHg0gUGBkiu/dM8VNODTRppso= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1NE5d0lxAdxXOL2nWwxUeL+Wf2ItY+N8jvCklovTdI8=; b=S2tTnfIhyhjiMTYW6twImEJHjmRfT4dZkl73wteMt96RlSx2gQrbLRJNY6ST9tpWHb hfcR7sGLlARObxiRZtO4OPBV7Lui9/4dB8NvNPXAOy3FgpTg4bDL/C113sVc/e86st6U tDuZeIufSkmeUPe0lvCJxKrKa6DMu61ntaOmJItNTrt8dvQflz/uAsfnQi5sF3DN9SKn SkbnceF1+SWhvoBZFkczKyHP5TptIcReZzxNtk15aUFF0CNAkztzfxkZbCXUvKK+qpgX zpFsLqUqikIc3rTaZSeBEXDa3Uk/tJtaPrWWNQ9ZoC/PLrgoLA4f2plrNC2myKj/izfS UJLw== X-Gm-Message-State: AFqh2krwgQJcneYiMJK8DDtFh2jh56kjwmf3TQ47ribBc9QpngFe/fpo y5db9Eyvbmqj0pzguyxCTkYzqASU+9WCXxlA X-Received: by 2002:a6b:d919:0:b0:6e9:9776:a6c8 with SMTP id r25-20020a6bd919000000b006e99776a6c8mr23184159ioc.2.1672169585446; Tue, 27 Dec 2022 11:33:05 -0800 (PST) Received: from markhas1.corp.google.com ([100.107.108.223]) by smtp.gmail.com with ESMTPSA id a10-20020a02ac0a000000b003755a721e98sm4504995jao.107.2022.12.27.11.33.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 27 Dec 2022 11:33:05 -0800 (PST) From: Mark Hasemeyer To: LKML Cc: Raul Rangel , Bhanu Prakash Maiya , Mark Hasemeyer , Krzysztof Kozlowski , Benson Leung , Guenter Roeck , Krzysztof Kozlowski , Lee Jones , Rob Herring , chrome-platform@lists.linux.dev, devicetree@vger.kernel.org Subject: [PATCH v13 2/3] dt-bindings: mfd: cros-ec: Add UART compatible string Date: Tue, 27 Dec 2022 12:32:23 -0700 Message-Id: <20221227123212.v13.2.I9e018ecb8bdf341648cb64417085978ff0d22a46@changeid> X-Mailer: git-send-email 2.39.0.314.g84b9a713c41-goog In-Reply-To: <20221227123212.v13.1.If7926fcbad397bc6990dd725690229bed403948c@changeid> References: <20221227123212.v13.1.If7926fcbad397bc6990dd725690229bed403948c@changeid> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Bhanu Prakash Maiya Add a compatible string to support the UART implementation of the cros ec interface. The driver does not support the reg and interrupt properties, so exempt them from being required for UART compatible nodes. Signed-off-by: Bhanu Prakash Maiya Co-developed-by: Mark Hasemeyer Signed-off-by: Mark Hasemeyer Acked-by: Krzysztof Kozlowski --- Changes in v13: - No change Changes in v12: - No change Changes in v11: - Update commit message to include device Changes in v10: - No change Changes in v9: - Rebase onto for-next - Update node-name from uart0 to serial - Remove reg and interrupt property requirement for UART compatible nodes. - Update authorship Changes in v8: - Update commit message Changes in v7: - No change Changes in v6: - No change Changes in v5: - No change Changes in v4: - Changes in commit message. Changes in v3: - Rebased changes on google,cros-ec.yaml Changes in v2: - No change --- .../bindings/mfd/google,cros-ec.yaml | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml index 3d5efa5578d1b..cdf1d719efe9d 100644 --- a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml +++ b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml @@ -33,6 +33,9 @@ properties: - description: For implementations of the EC connected through RPMSG. const: google,cros-ec-rpmsg + - description: + For implementations of the EC connected through UART. + const: google,cros-ec-uart controller-data: true @@ -187,6 +190,15 @@ allOf: properties: mediatek,rpmsg-name: false + - if: + properties: + compatible: + not: + contains: + enum: + - google,cros-ec-rpmsg + - google,cros-ec-uart + then: required: - reg - interrupts @@ -299,4 +311,12 @@ examples: vdd-supply = <&pp3300_fp_mcu>; }; }; + + # Example for UART + - | + serial { + cros-ec { + compatible = "google,cros-ec-uart"; + }; + }; ... -- 2.39.0.314.g84b9a713c41-goog