public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Lee Jones" <lee@kernel.org>, "Pavel Machek" <pavel@kernel.org>,
	"Sebastian Reichel" <sre@kernel.org>,
	"Ion Agorria" <ion@agorria.com>,
	"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org, linux-leds@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 1/7] dt-bindings: embedded-controller: document ASUS Transformer EC
Date: Mon, 16 Feb 2026 18:04:44 +0000	[thread overview]
Message-ID: <20260216-sprung-scallop-de7b64bf528c@spud> (raw)
In-Reply-To: <20260214180959.30714-2-clamor95@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4354 bytes --]

On Sat, Feb 14, 2026 at 08:09:53PM +0200, Svyatoslav Ryhel wrote:
> Document embedded controller used in ASUS Transformer device series.
> 
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
>  .../asus,transformer-ec.yaml                  | 98 +++++++++++++++++++
>  1 file changed, 98 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/embedded-controller/asus,transformer-ec.yaml
> 
> diff --git a/Documentation/devicetree/bindings/embedded-controller/asus,transformer-ec.yaml b/Documentation/devicetree/bindings/embedded-controller/asus,transformer-ec.yaml
> new file mode 100644
> index 000000000000..670c4c2d339d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/embedded-controller/asus,transformer-ec.yaml
> @@ -0,0 +1,98 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/embedded-controller/asus,transformer-ec.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ASUS Transformer's Embedded Controller
> +
> +description:
> +  Several Nuvoton based Embedded Controllers attached to an I2C bus,
> +  running a custom ASUS firmware, specific to the ASUS Transformer
> +  device series.
> +
> +maintainers:
> +  - Svyatoslav Ryhel <clamor95@gmail.com>
> +
> +allOf:
> +  - $ref: /schemas/power/supply/power-supply.yaml
> +
> +properties:
> +  compatible:
> +    oneOf:
> +      - enum:
> +          - asus,p1801-t-ec-pad
> +          - asus,sl101-ec-dock
> +          - asus,tf600t-ec-pad
> +          - asus,tf701t-ec-pad
> +
> +      - items:
> +          - enum:
> +              - asus,tf101-ec-dock
> +              - asus,tf101g-ec-dock
> +              - asus,tf201-ec-dock
> +              - asus,tf300t-ec-dock
> +              - asus,tf300tg-ec-dock
> +              - asus,tf300tl-ec-dock
> +              - asus,tf700t-ec-dock
> +          - const: asus,transformer-ec-dock
> +
> +      - items:
> +          - enum:
> +              - asus,tf201-ec-pad
> +              - asus,tf300t-ec-pad
> +              - asus,tf300tg-ec-pad
> +              - asus,tf300tl-ec-pad
> +              - asus,tf700t-ec-pad
> +          - const: asus,transformer-ec-pad

Can you explain somewhere here what the "dock" and "pad" devices are and
how they differ? For example, I am currently wondering why tf700t has both
"dock" and "pad".
Also, why are some of the compatibles permitted standalone? That should
be mentioned in your commit message too. Also, other than the sl101, the
standalone ones seem to have the same match data in the mfd driver. Why
are fallbacks not made use of there?

Since this transformer series seems to have multiple programming models
for "ec-pad" devices, it calls into question your use of the generic
fallback compatibles is appropriate and makes it seem like you should be
using device compatibles as a fallback.

The rest looks okay other than the filename, which doesn't match any of
the compatibles that you've got here.

Cheers,
Conor.

> +
> +  reg:
> +    description:
> +      The ASUS Transformer EC has a main I2C address and an associated
> +      DockRAM device, which provides power-related functions for the
> +      embedded controller. Both addresses are required for operation.
> +    minItems: 2
> +
> +  reg-names:
> +    items:
> +      - const: ec
> +      - const: dockram
> +
> +  interrupts:
> +    maxItems: 1
> +
> +  request-gpios:
> +    maxItems: 1
> +
> +required:
> +  - compatible
> +  - reg
> +  - reg-names
> +  - interrupts
> +  - request-gpios
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/gpio/gpio.h>
> +    #include <dt-bindings/interrupt-controller/irq.h>
> +
> +    i2c {
> +      #address-cells = <1>;
> +      #size-cells = <0>;
> +
> +      embedded-controller@19 {
> +        compatible = "asus,tf201-ec-dock", "asus,transformer-ec-dock";
> +        reg = <0x19>, <0x1b>;
> +        reg-names = "ec", "dockram";
> +
> +        interrupt-parent = <&gpio>;
> +        interrupts = <151 IRQ_TYPE_LEVEL_LOW>;
> +
> +        request-gpios = <&gpio 134 GPIO_ACTIVE_LOW>;
> +
> +        monitored-battery = <&dock_battery>;
> +      };
> +    };
> +...
> -- 
> 2.51.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-02-16 18:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14 18:09 [PATCH v3 0/7] mfd: Add support for Asus Transformer embedded controller Svyatoslav Ryhel
2026-02-14 18:09 ` [PATCH v3 1/7] dt-bindings: embedded-controller: document ASUS Transformer EC Svyatoslav Ryhel
2026-02-16 18:04   ` Conor Dooley [this message]
2026-02-16 18:22     ` Svyatoslav Ryhel
2026-02-16 18:50       ` Conor Dooley
2026-02-16 19:14         ` Svyatoslav Ryhel
2026-02-17 11:05           ` Conor Dooley
2026-02-17 11:23             ` Svyatoslav Ryhel
2026-02-17 11:32               ` Krzysztof Kozlowski
2026-02-17 11:34                 ` Svyatoslav Ryhel
2026-02-17 14:03                   ` Conor Dooley
2026-02-17 14:29                     ` Svyatoslav Ryhel
2026-02-17 14:44                       ` Krzysztof Kozlowski
2026-02-17 15:50                       ` Conor Dooley
2026-02-17 14:01               ` Conor Dooley
2026-02-17 11:31             ` Krzysztof Kozlowski
2026-02-14 18:09 ` [PATCH v3 2/7] mfd: Add driver for ASUS Transformer embedded controller Svyatoslav Ryhel
2026-02-15 20:28   ` kernel test robot
2026-02-16  4:57   ` kernel test robot
2026-02-14 18:09 ` [PATCH v3 3/7] input: serio: Add driver for ASUS Transformer dock keyboard and touchpad Svyatoslav Ryhel
2026-02-14 18:09 ` [PATCH v3 4/7] input: keyboard: Add driver for ASUS Transformer dock multimedia keys Svyatoslav Ryhel
2026-02-14 18:09 ` [PATCH v3 5/7] leds: Add driver for ASUS Transformer LEDs Svyatoslav Ryhel
2026-02-14 18:09 ` [PATCH v3 6/7] power: supply: Add driver for ASUS Transformer battery Svyatoslav Ryhel
2026-02-14 18:09 ` [PATCH v3 7/7] power: supply: Add charger driver for Asus Transformers Svyatoslav Ryhel

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=20260216-sprung-scallop-de7b64bf528c@spud \
    --to=conor@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=ion@agorria.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=pavel@kernel.org \
    --cc=robh@kernel.org \
    --cc=sre@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