Message ID | 20221207104005.v10.2.I9e018ecb8bdf341648cb64417085978ff0d22a46@changeid |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp322305wrr; Wed, 7 Dec 2022 09:48:44 -0800 (PST) X-Google-Smtp-Source: AA0mqf5ghO2a3aNrhMfLKiNGwZobrL1InnTimJF6KLVz68pWidyilbl5sQlo3SD8AL2XK9CZWxX5 X-Received: by 2002:a17:906:6dd7:b0:7a1:1c24:e564 with SMTP id j23-20020a1709066dd700b007a11c24e564mr65306763ejt.629.1670435323825; Wed, 07 Dec 2022 09:48:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670435323; cv=none; d=google.com; s=arc-20160816; b=F+Y1SSOO5ky/o1yZKgl6OokuWhNwzc61WfVFQ6WnEgT6huybnqKS7s5537ZCFfoq/Z RMzaUC1bvFFtteAkrUw6AmMrgz9Jnlc2pJeyYLfcWXgMfrdux6JdlwjMamP1+qpq/w/6 rg2w5cDhjVn+HqID9jmcOjJZrrmkJspP9R5CyArZ73rHpzNdP/yN1psvUB535X9yhdGD XakihQy4La0bGRZF/x5Pe5ptYVkyU3N1FMoG3L7IUEoR6BmUenblkaqxhx8kkNKABlkJ ke7+On22ZFSMy5P51/pRqW3aiFKdGWxH445UrRqNXgv4m9efe19NcGxUukvEggdXfoqT YWaQ== 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=wQHZD5UNbZreX1XKl32tTP9ac2aVItlytgfwhZVebO8=; b=jOuR5W5Thbnf2XfKI9CG971MM/uHvtZp1CWPgyvq+L/vZN+fp+NQ0yBvkXvwuBFTjD /02MryoZwkvGxVmQqmFri44ji4QZdWE2WAXzfk4n1QtO90t6TYfrkUE1q5CD7rChHLhz KDtUET1VmwuXZxvw9iHiaFxZ9tRFmQ62ACc5VVurfH5eqGmzzDi7KQDFiu7acFRvZS5L bkENlfEiahjlFf30BwKo02RwSmqBvOvpmXZNW7AkI6FEvalcn7/5sV7anh1vMmP3r1Dw mimSlzHLfq+eMzKWYDkkHST9SCF1tVbiH2u+BjMLCY3e4P1JU6NwGMG4TS2w1jpAOIV5 L7kw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=nfMziSmw; 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: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y14-20020a056402134e00b0046cadaade54si4388138edw.619.2022.12.07.09.48.20; Wed, 07 Dec 2022 09:48:43 -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=nfMziSmw; 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 S229961AbiLGRkc (ORCPT <rfc822;foxyelen666@gmail.com> + 99 others); Wed, 7 Dec 2022 12:40:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46474 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229691AbiLGRk0 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 7 Dec 2022 12:40:26 -0500 Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 778CBDEAD for <linux-kernel@vger.kernel.org>; Wed, 7 Dec 2022 09:40:25 -0800 (PST) Received: by mail-io1-xd36.google.com with SMTP id n63so7778492iod.7 for <linux-kernel@vger.kernel.org>; Wed, 07 Dec 2022 09:40:25 -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=wQHZD5UNbZreX1XKl32tTP9ac2aVItlytgfwhZVebO8=; b=nfMziSmw5P+4LBSK8oTS4a1Ei4qOzUCAycEf4tw+5EKwugQb5WMaVK7RgNTBMBFeop BS6NtYrAbd9kBacwGq7qBk0QZ1sNHfGBByf8Nvim+JThNEVQs1aodka41eaK0K2cQl6R UGUYF6kSEkla0mvtqN2svnmz8Bk/SpTqp6BV8= 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=wQHZD5UNbZreX1XKl32tTP9ac2aVItlytgfwhZVebO8=; b=gBJ1+7OOuE+VStJFvN978djOTAlnRZwIe4vc19FR6qYqtPGQhThCkr9syEbGEMIRl4 a/XrSMtCRt5+b5pcnet444Z9r6toCdcSP+L2Zm2mTzs79OpPbQxtKT9kZvhK+0SaFqLp Xacy3jtHpZgBR/i8Sf746BgK9YW3V5UVGYhzJjzweN6XTxU9NCpqFK2Yn1HvKP0wwWTw ybpAJnpN1NylFY9mJZwXbZIteqypV/VLt3Z0I8sEFxcekq3IV6ZZsLkpWusawg2yHBCy AwJJkOywL0ANEZj6fQdWQimz+2O9blbuMpRthUyfJ8afBziqNChysE5x3NotTLl6o6vi a8qQ== X-Gm-Message-State: ANoB5plGcOJuy0SA4oClUcJsManoDi+JB1nQwzNJUaykrSok9Q9KfaU0 Uthv4tQBJwiL659Qxiu9SkvRgeuuxXWyjgKL X-Received: by 2002:a5d:8492:0:b0:6df:bdc1:2421 with SMTP id t18-20020a5d8492000000b006dfbdc12421mr16403038iom.116.1670434824777; Wed, 07 Dec 2022 09:40:24 -0800 (PST) Received: from markhas1.roam.corp.google.com (63-225-246-100.hlrn.qwest.net. [63.225.246.100]) by smtp.gmail.com with ESMTPSA id q18-20020a920512000000b0030341bffab8sm32782ile.31.2022.12.07.09.40.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 07 Dec 2022 09:40:24 -0800 (PST) From: Mark Hasemeyer <markhas@chromium.org> To: LKML <linux-kernel@vger.kernel.org> Cc: Raul Rangel <rrangel@chromium.org>, Bhanu Prakash Maiya <bhanumaiya@chromium.org>, Mark Hasemeyer <markhas@chromium.org>, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Benson Leung <bleung@chromium.org>, Guenter Roeck <groeck@chromium.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>, chrome-platform@lists.linux.dev, devicetree@vger.kernel.org Subject: [PATCH v10 2/3] dt-bindings: mfd: Add compatible string for UART support Date: Wed, 7 Dec 2022 10:40:12 -0700 Message-Id: <20221207104005.v10.2.I9e018ecb8bdf341648cb64417085978ff0d22a46@changeid> X-Mailer: git-send-email 2.39.0.rc1.256.g54fd8350bd-goog In-Reply-To: <20221207104005.v10.1.If7926fcbad397bc6990dd725690229bed403948c@changeid> References: <20221207104005.v10.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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1751578390077210994?= X-GMAIL-MSGID: =?utf-8?q?1751578390077210994?= |
Series |
[v10,1/3] platform/chrome: cros_ec_uart: Add cros-ec-uart transport layer
|
|
Commit Message
Mark Hasemeyer
Dec. 7, 2022, 5:40 p.m. UTC
From: Bhanu Prakash Maiya <bhanumaiya@chromium.org> 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 <bhanumaiya@chromium.org> Co-developed-by: Mark Hasemeyer <markhas@chromium.org> Signed-off-by: Mark Hasemeyer <markhas@chromium.org> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> --- 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(+)
Comments
On 07/12/2022 18:40, Mark Hasemeyer wrote: > From: Bhanu Prakash Maiya <bhanumaiya@chromium.org> > > 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 <bhanumaiya@chromium.org> > Co-developed-by: Mark Hasemeyer <markhas@chromium.org> > Signed-off-by: Mark Hasemeyer <markhas@chromium.org> > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Use subject prefixes matching the subsystem (git log --oneline -- ...) and device. Currently it looks like you change ENTIRE MFD subsystem. > --- > > Changes in v10: > - No change > Best regards, Krzysztof
On Wed, 07 Dec 2022, Mark Hasemeyer wrote: > From: Bhanu Prakash Maiya <bhanumaiya@chromium.org> > > 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 <bhanumaiya@chromium.org> > Co-developed-by: Mark Hasemeyer <markhas@chromium.org> > Signed-off-by: Mark Hasemeyer <markhas@chromium.org> > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > --- > > 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(+) I changed the subject line and applied the patch, thanks.
On Wed, Jan 04, 2023 at 04:08:24PM +0000, Lee Jones wrote: > On Wed, 07 Dec 2022, Mark Hasemeyer wrote: > > > From: Bhanu Prakash Maiya <bhanumaiya@chromium.org> > > > > 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 <bhanumaiya@chromium.org> > > Co-developed-by: Mark Hasemeyer <markhas@chromium.org> > > Signed-off-by: Mark Hasemeyer <markhas@chromium.org> > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > --- > > > > Changes in v10: > > - No change > > [...] > > I changed the subject line and applied the patch, thanks. Pardon me. I didn't know you would pick the patch so that I have queued it into chrome-platform[1]. Would you like me to drop the commit? [1]: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git/commit/?h=for-next&id=5be8cd61dcddfaee5d92072073672037154e76f5
On Thu, 05 Jan 2023, Tzung-Bi Shih wrote: > On Wed, Jan 04, 2023 at 04:08:24PM +0000, Lee Jones wrote: > > On Wed, 07 Dec 2022, Mark Hasemeyer wrote: > > > > > From: Bhanu Prakash Maiya <bhanumaiya@chromium.org> > > > > > > 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 <bhanumaiya@chromium.org> > > > Co-developed-by: Mark Hasemeyer <markhas@chromium.org> > > > Signed-off-by: Mark Hasemeyer <markhas@chromium.org> > > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > --- > > > > > > Changes in v10: > > > - No change > > > > [...] > > > > I changed the subject line and applied the patch, thanks. > > Pardon me. I didn't know you would pick the patch so that I have queued it > into chrome-platform[1]. Would you like me to drop the commit? > > [1]: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git/commit/?h=for-next&id=5be8cd61dcddfaee5d92072073672037154e76f5
On Thu, 05 Jan 2023, Tzung-Bi Shih wrote: > On Wed, Jan 04, 2023 at 04:08:24PM +0000, Lee Jones wrote: > > On Wed, 07 Dec 2022, Mark Hasemeyer wrote: > > > > > From: Bhanu Prakash Maiya <bhanumaiya@chromium.org> > > > > > > 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 <bhanumaiya@chromium.org> > > > Co-developed-by: Mark Hasemeyer <markhas@chromium.org> > > > Signed-off-by: Mark Hasemeyer <markhas@chromium.org> > > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > --- > > > > > > Changes in v10: > > > - No change > > > > [...] > > > > I changed the subject line and applied the patch, thanks. > > Pardon me. I didn't know you would pick the patch so that I have queued it > into chrome-platform[1]. Would you like me to drop the commit? Yes, please do. You should gain permission from the maintainer before you apply patches. % scripts/get_maintainer.pl -f Documentation/devicetree/bindings/mfd/google,cros-ec.yaml Lee Jones <lee@kernel.org> (supporter:MULTIFUNCTION DEVICES (MFD)) Rob Herring <robh+dt@kernel.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) Matthias Brugger <matthias.bgg@gmail.com> (maintainer:ARM/Mediatek SoC support) Why do I get the feeling we've had this conversation before?
On Thu, Jan 05, 2023 at 02:24:26PM +0000, Lee Jones wrote: > On Thu, 05 Jan 2023, Tzung-Bi Shih wrote: > > > On Wed, Jan 04, 2023 at 04:08:24PM +0000, Lee Jones wrote: > > > On Wed, 07 Dec 2022, Mark Hasemeyer wrote: > > > > > > > From: Bhanu Prakash Maiya <bhanumaiya@chromium.org> > > > > > > > > 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 <bhanumaiya@chromium.org> > > > > Co-developed-by: Mark Hasemeyer <markhas@chromium.org> > > > > Signed-off-by: Mark Hasemeyer <markhas@chromium.org> > > > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > > --- > > > > > > > > Changes in v10: > > > > - No change > > > > > > [...] > > > > > > I changed the subject line and applied the patch, thanks. > > > > Pardon me. I didn't know you would pick the patch so that I have queued it > > into chrome-platform[1]. Would you like me to drop the commit? > > Yes, please do. Dropped in chrome-platform. > You should gain permission from the maintainer before you apply patches. > > % scripts/get_maintainer.pl -f Documentation/devicetree/bindings/mfd/google,cros-ec.yaml > Lee Jones <lee@kernel.org> (supporter:MULTIFUNCTION DEVICES (MFD)) > Rob Herring <robh+dt@kernel.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > Matthias Brugger <matthias.bgg@gmail.com> (maintainer:ARM/Mediatek SoC support) I see. I guess for the case, I should get both MFD and DT bindings maintainers' Acks before applying the patch.
On Thu, 05 Jan 2023, Tzung-Bi Shih wrote: > On Thu, Jan 05, 2023 at 02:24:26PM +0000, Lee Jones wrote: > > On Thu, 05 Jan 2023, Tzung-Bi Shih wrote: > > > > > On Wed, Jan 04, 2023 at 04:08:24PM +0000, Lee Jones wrote: > > > > On Wed, 07 Dec 2022, Mark Hasemeyer wrote: > > > > > > > > > From: Bhanu Prakash Maiya <bhanumaiya@chromium.org> > > > > > > > > > > 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 <bhanumaiya@chromium.org> > > > > > Co-developed-by: Mark Hasemeyer <markhas@chromium.org> > > > > > Signed-off-by: Mark Hasemeyer <markhas@chromium.org> > > > > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > > > --- > > > > > > > > > > Changes in v10: > > > > > - No change > > > > > > > > [...] > > > > > > > > I changed the subject line and applied the patch, thanks. > > > > > > Pardon me. I didn't know you would pick the patch so that I have queued it > > > into chrome-platform[1]. Would you like me to drop the commit? > > > > Yes, please do. > > Dropped in chrome-platform. > > > You should gain permission from the maintainer before you apply patches. > > > > % scripts/get_maintainer.pl -f Documentation/devicetree/bindings/mfd/google,cros-ec.yaml > > Lee Jones <lee@kernel.org> (supporter:MULTIFUNCTION DEVICES (MFD)) > > Rob Herring <robh+dt@kernel.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > Matthias Brugger <matthias.bgg@gmail.com> (maintainer:ARM/Mediatek SoC support) > > I see. I guess for the case, I should get both MFD and DT bindings > maintainers' Acks before applying the patch. Yes. The situation isn't overly clear and differs from subsystem to subsystem and maintainer to maintainer. In the MFD case, Rob and Krzysztof conduct the first reviews. 99 times out of 100, if they're happy, I'm happy and I merge the changes via the MFD tree. Same goes for Backlight and more recently, LEDs.
On Thu, Jan 05, 2023 at 04:27:32PM +0000, Lee Jones wrote: > > > You should gain permission from the maintainer before you apply patches. > > > > > > % scripts/get_maintainer.pl -f Documentation/devicetree/bindings/mfd/google,cros-ec.yaml > > > Lee Jones <lee@kernel.org> (supporter:MULTIFUNCTION DEVICES (MFD)) > > > Rob Herring <robh+dt@kernel.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > > Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > > Matthias Brugger <matthias.bgg@gmail.com> (maintainer:ARM/Mediatek SoC support) > > > > I see. I guess for the case, I should get both MFD and DT bindings > > maintainers' Acks before applying the patch. > > Yes. The situation isn't overly clear and differs from subsystem to > subsystem and maintainer to maintainer. In the MFD case, Rob and > Krzysztof conduct the first reviews. 99 times out of 100, if they're > happy, I'm happy and I merge the changes via the MFD tree. Same goes > for Backlight and more recently, LEDs. I see. Apologize for that and I will pay more attention next time when handling cross-subsystem patches.
On Wed, Jan 4, 2023 at 9:08 AM Lee Jones <lee@kernel.org> wrote: > I changed the subject line and applied the patch, thanks. Hey Lee, a couple comments/questions: 1. The subject line of this patch was updated in v11 of the series. 2. What tree was the patch applied to? I don't see the changes in linux-next. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml On Thu, Jan 5, 2023 at 11:08 AM Tzung-Bi Shih <tzungbi@kernel.org> wrote: > > On Thu, Jan 05, 2023 at 04:27:32PM +0000, Lee Jones wrote: > > > > You should gain permission from the maintainer before you apply patches. > > > > > > > > % scripts/get_maintainer.pl -f Documentation/devicetree/bindings/mfd/google,cros-ec.yaml > > > > Lee Jones <lee@kernel.org> (supporter:MULTIFUNCTION DEVICES (MFD)) > > > > Rob Herring <robh+dt@kernel.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > > > Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> (maintainer:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS) > > > > Matthias Brugger <matthias.bgg@gmail.com> (maintainer:ARM/Mediatek SoC support) > > > > > > I see. I guess for the case, I should get both MFD and DT bindings > > > maintainers' Acks before applying the patch. > > > > Yes. The situation isn't overly clear and differs from subsystem to > > subsystem and maintainer to maintainer. In the MFD case, Rob and > > Krzysztof conduct the first reviews. 99 times out of 100, if they're > > happy, I'm happy and I merge the changes via the MFD tree. Same goes > > for Backlight and more recently, LEDs. > > I see. Apologize for that and I will pay more attention next time when > handling cross-subsystem patches.
On Mon, 09 Jan 2023, Mark Hasemeyer wrote: > On Wed, Jan 4, 2023 at 9:08 AM Lee Jones <lee@kernel.org> wrote: > > I changed the subject line and applied the patch, thanks. > > Hey Lee, a couple comments/questions: > 1. The subject line of this patch was updated in v11 of the series. > 2. What tree was the patch applied to? I don't see the changes in linux-next. > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml Thanks for flagging. You will do tomorrow.
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"; + }; + }; ...