From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>, robh@kernel.org
Cc: kernel@collabora.com, bleung@chromium.org, groeck@chromium.org,
sjg@chromium.org, dianders@chromium.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] dt-bindings: mfd: google,cros-ec: add missing properties
Date: Mon, 5 Oct 2020 11:23:15 +0200 [thread overview]
Message-ID: <a6132b1e-7613-35c2-f450-e3ca300ab49b@collabora.com> (raw)
In-Reply-To: <20201005071403.17450-4-ricardo.canuelo@collabora.com>
Hi Ricardo,
Thank you to work on this.
On 5/10/20 9:14, Ricardo Cañuelo wrote:
> Add missing properties that are currently used in the examples of
> subnode bindings and in many DTs.
> This fixes all current dt_binding_check and dtbs_check warnings related
> to this binding.
>
> Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com>
> ---
> .../bindings/mfd/google,cros-ec.yaml | 40 +++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> index f49c0d5d31ad..c2dc05cdef9f 100644
> --- a/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> +++ b/Documentation/devicetree/bindings/mfd/google,cros-ec.yaml
> @@ -59,18 +59,58 @@ properties:
> whether this nvram is present or not.
> type: boolean
>
> + mtk,rpmsg-name:
AFAIK mtk is not a valid vendor prefix (vendor-prefixes.yaml), so I am wondering
if this should be mediatek,rpmsg-name. I see this being used in
drivers/rpmsg/mtk_rpmsg.c file, but there isn't a devitree using it. So maybe
we're on time to fix it.
Thanks,
Enric
> + 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.
>
> reg:
> maxItems: 1
>
> + '#address-cells':
> + enum: [1, 2]
> +
> + '#size-cells':
> + enum: [0, 1]
> +
> interrupts:
> maxItems: 1
>
> 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#"
> +
> +patternProperties:
> + "^regulator@[a-f0-9]+$":
> + type: object
> + $ref: "/schemas/regulator/google,cros-ec-regulator.yaml#"
> +
> + "^extcon[0-9]*$":
> + type: object
> + $ref: "/schemas/extcon/extcon-usbc-cros-ec.yaml#"
> +
> + "^ec-codec@[a-f0-9]+$":
> + type: object
> + $ref: "/schemas/sound/google,cros-ec-codec.yaml#"
> +
> + "^i2c-tunnel[0-9]*$":
> + type: object
> + $ref: "/schemas/i2c/google,cros-ec-i2c-tunnel.yaml#"
> +
> required:
> - compatible
>
>
next prev parent reply other threads:[~2020-10-05 9:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 7:13 [PATCH 0/3] Fix checker warnings related to cros-ec binding Ricardo Cañuelo
2020-10-05 7:14 ` [PATCH 1/3] dt-bindings: i2c: convert i2c-cros-ec-tunnel to json-schema Ricardo Cañuelo
2020-10-05 8:52 ` Enric Balletbo i Serra
2020-10-05 9:18 ` Ricardo Cañuelo
2020-10-05 9:27 ` Enric Balletbo i Serra
2020-10-05 14:04 ` Rob Herring
2020-10-05 7:14 ` [PATCH 2/3] dt-bindings: input: convert cros-ec-keyb " Ricardo Cañuelo
2020-10-05 9:03 ` Enric Balletbo i Serra
2020-10-05 9:35 ` Ricardo Cañuelo
2020-10-05 7:14 ` [PATCH 3/3] dt-bindings: mfd: google,cros-ec: add missing properties Ricardo Cañuelo
2020-10-05 9:23 ` Enric Balletbo i Serra [this message]
2020-10-05 9:48 ` Ricardo Cañuelo
2020-10-05 15:37 ` Rob Herring
2020-10-05 15:48 ` Enric Balletbo i Serra
2020-10-06 6:13 ` Ricardo Cañuelo
2020-10-06 11:28 ` Guenter Roeck
2020-10-06 13:07 ` Ricardo Cañuelo
2020-10-06 21:35 ` Rob Herring
2020-10-07 6:31 ` Ricardo Cañuelo
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=a6132b1e-7613-35c2-f450-e3ca300ab49b@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=kernel@collabora.com \
--cc=ricardo.canuelo@collabora.com \
--cc=robh@kernel.org \
--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).