From: Rob Herring <robh@kernel.org>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
Cc: kernel@collabora.com, enric.balletbo@collabora.com,
bleung@chromium.org, groeck@chromium.org, sjg@chromium.org,
dianders@chromium.org, devicetree@vger.kernel.org,
dmitry.torokhov@gmail.com
Subject: Re: [PATCH v2 3/3] mfd: google,cros-ec: add missing properties
Date: Thu, 8 Oct 2020 13:38:18 -0500 [thread overview]
Message-ID: <20201008183818.GB2395464@bogus> (raw)
In-Reply-To: <20201008102825.3812-4-ricardo.canuelo@collabora.com>
On Thu, Oct 08, 2020 at 12:28:25PM +0200, Ricardo Cañuelo wrote:
> Add missing properties that are currently used in the examples of
> subnode bindings and in many DTs.
>
> Also updates the example in sound/google,cros-ec-codec.yaml to comply
> with the google,cros-ec binding.
>
> Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
> ---
> .../bindings/mfd/google,cros-ec.yaml | 42 +++++++++++++++++++
> .../bindings/sound/google,cros-ec-codec.yaml | 26 +++++++-----
> 2 files changed, 58 insertions(+), 10 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> index 351bfb6d37ba..48929bb07d98 100644
> --- a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> +++ b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> @@ -59,6 +59,14 @@ properties:
> whether this nvram is present or not.
> type: boolean
>
> + mtk,rpmsg-name:
> + description:
> + Must be defined if the cros-ec is a rpmsg device for a Mediatek
> + ARM Cortex M4 Co-processor. Contains the name pf the rpmsg
> + device. Used to match the subnode to the rpmsg device announced by
> + the SCP.
> + $ref: "/schemas/types.yaml#/definitions/string"
> +
> spi-max-frequency:
> description: Maximum SPI frequency of the device in Hz.
>
> @@ -71,14 +79,48 @@ properties:
> wakeup-source:
> description: Button can wake-up the system.
>
> + typec:
> + $ref: "/schemas/chrome/google,cros-ec-typec.yaml#"
> +
> + ec-pwm:
> + $ref: "/schemas/pwm/google,cros-ec-pwm.yaml#"
> +
> keyboard-controller:
> $ref: "/schemas/input/google,cros-ec-keyb.yaml#"
>
> + codecs:
Doesn't moving this require a driver change?
If you only need 1 codec, then just drop the unit-address.
> + type: object
> + additionalProperties: false
> +
> + properties:
> + '#address-cells':
> + const: 2
> +
> + '#size-cells':
> + const: 1
> +
> + patternProperties:
> + "^ec-codec@[a-f0-9]+$":
> + type: object
> + $ref: "/schemas/sound/google,cros-ec-codec.yaml#"
> +
> + required:
> + - "#address-cells"
> + - "#size-cells"
> +
> patternProperties:
> "^i2c-tunnel[0-9]*$":
> type: object
> $ref: "/schemas/i2c/google,cros-ec-i2c-tunnel.yaml#"
>
> + "^regulator@[0-9]+$":
> + type: object
> + $ref: "/schemas/regulator/google,cros-ec-regulator.yaml#"
> +
> + "^extcon[0-9]*$":
> + type: object
> + $ref: "/schemas/extcon/extcon-usbc-cros-ec.yaml#"
> +
> required:
> - compatible
>
> diff --git a/Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml b/Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml
> index c84e656afb0a..acfb9db021dc 100644
> --- a/Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml
> +++ b/Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml
> @@ -11,9 +11,10 @@ maintainers:
>
> description: |
> Google's ChromeOS EC codec is a digital mic codec provided by the
> - Embedded Controller (EC) and is controlled via a host-command interface.
> - An EC codec node should only be found as a sub-node of the EC node (see
> - Documentation/devicetree/bindings/mfd/cros-ec.txt).
> + Embedded Controller (EC) and is controlled via a host-command
> + interface. An EC codec node should only be found inside the "codecs"
> + subnode of a cros-ec node.
> + (see Documentation/devicetree/bindings/mfd/google,cros-ec.yaml).
>
> properties:
> compatible:
> @@ -54,14 +55,19 @@ examples:
> #size-cells = <0>;
> cros-ec@0 {
> compatible = "google,cros-ec-spi";
> - #address-cells = <2>;
> - #size-cells = <1>;
> reg = <0>;
> - cros_ec_codec: ec-codec@10500000 {
> - compatible = "google,cros-ec-codec";
> - #sound-dai-cells = <1>;
> - reg = <0x0 0x10500000 0x80000>;
> - memory-region = <&reserved_mem>;
> +
> + codecs {
> + #address-cells = <2>;
> + #size-cells = <1>;
> +
> + cros_ec_codec: ec-codec@10500000 {
> + compatible = "google,cros-ec-codec";
> + #sound-dai-cells = <1>;
> + reg = <0x0 0x10500000 0x80000>;
> + memory-region = <&reserved_mem>;
> + };
> +
> };
> };
> };
> --
> 2.18.0
>
next prev parent reply other threads:[~2020-10-08 18:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 10:28 [PATCH v2 0/3] Fix checker warnings related to cros-ec binding Ricardo Cañuelo
2020-10-08 10:28 ` [PATCH v2 1/3] dt-bindings: i2c: convert i2c-cros-ec-tunnel to json-schema Ricardo Cañuelo
2020-10-11 11:17 ` Enric Balletbo i Serra
2020-10-08 10:28 ` [PATCH v2 2/3] dt-bindings: input: convert cros-ec-keyb " Ricardo Cañuelo
2020-10-08 18:32 ` Rob Herring
2020-10-09 5:28 ` Ricardo Cañuelo
2020-10-09 13:23 ` Rob Herring
2020-10-08 10:28 ` [PATCH v2 3/3] mfd: google,cros-ec: add missing properties Ricardo Cañuelo
2020-10-08 18:38 ` Rob Herring [this message]
2020-10-09 5:48 ` Ricardo Cañuelo
2020-10-09 13:34 ` Rob Herring
2020-10-13 6:46 ` Ricardo Cañuelo
2020-10-14 2:18 ` Tzung-Bi Shih
2020-10-15 6:52 ` Ricardo Cañuelo
2020-10-15 8:25 ` Enric Balletbo i Serra
2020-10-15 9:50 ` Tzung-Bi Shih
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=20201008183818.GB2395464@bogus \
--to=robh@kernel.org \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=kernel@collabora.com \
--cc=ricardo.canuelo@collabora.com \
--cc=sjg@chromium.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).