From: Krzysztof Kozlowski <krzk@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: "Lee Jones" <lee@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Pavel Machek" <pavel@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sebastian Reichel" <sre@kernel.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Ion Agorria" <ion@agorria.com>,
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 v2 3/9] dt-bindings: mfd: document ASUS Transformer EC
Date: Tue, 10 Feb 2026 12:54:01 +0100 [thread overview]
Message-ID: <ec3b39d6-51ec-429d-b083-e5af2b4a9c65@kernel.org> (raw)
In-Reply-To: <CAPVz0n0u_0ZukcKXt0QpiyCMhWsg2VE-dE19wDCbRQvBvVOf+A@mail.gmail.com>
On 10/02/2026 12:40, Svyatoslav Ryhel wrote:
>>>
>>> So you propose introduce a compatible for every single ec used in
>>> transformers instead of simply disable unpopulated functions? And how
>>> then battery and charger can reach monitored cell if they have no
>>> dedicated node?
>>
>> Just like for other bindings for nodes without resources, fold into
>> parent. This is already explained in writing bindings, so you could have
>> just read that. I will pass with answering more questions till you read
>> that doc.
>>
>
> Unfolding asus,ec-pad and asus,ec-dock will result in this list:
>
> asus,tf101-dock-ec
> asus,tf101g-dock-ec
> asus,sl101-pad-ec
> asus,tf201-pad-ec
> asus,tf201-dock-ec
> asus,tf300t-pad-ec
> asus,tf300t-dock-ec
> asus,tf300tg-pad-ec
> asus,tf300tg-dock-ec
> asus,tf300tl-pad-ec
> asus,tf300tl-dock-ec
> asus,tf600t-pad-ec
> asus,tf700t-pad-ec
> asus,tf700t-dock-ec
> asus,tf701t-pad-ec
> asus,p1801-t-pad-ec
>
> with minor variations in populated cells. Is this acceptible?
Yes, this looks correct.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-10 11:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 10:43 [PATCH v2 0/9] mfd: Add support for Asus Transformer embedded controller Svyatoslav Ryhel
2026-02-09 10:43 ` [PATCH v2 1/9] dt-bindings: misc: document ASUS Transformers EC DockRAM Svyatoslav Ryhel
2026-02-10 9:25 ` Krzysztof Kozlowski
2026-02-10 9:42 ` Svyatoslav Ryhel
2026-02-10 10:50 ` Krzysztof Kozlowski
2026-02-10 11:08 ` Svyatoslav Ryhel
2026-02-09 10:44 ` [PATCH v2 2/9] misc: Support Asus Transformer's EC access device Svyatoslav Ryhel
2026-02-09 10:44 ` [PATCH v2 3/9] dt-bindings: mfd: document ASUS Transformer EC Svyatoslav Ryhel
2026-02-10 9:22 ` Krzysztof Kozlowski
2026-02-10 9:37 ` Svyatoslav Ryhel
2026-02-10 10:48 ` Krzysztof Kozlowski
2026-02-10 10:59 ` Svyatoslav Ryhel
2026-02-10 11:04 ` Krzysztof Kozlowski
2026-02-10 11:14 ` Svyatoslav Ryhel
2026-02-10 11:24 ` Krzysztof Kozlowski
2026-02-10 11:40 ` Svyatoslav Ryhel
2026-02-10 11:54 ` Krzysztof Kozlowski [this message]
2026-02-10 12:48 ` Krzysztof Kozlowski
2026-02-11 10:48 ` Svyatoslav Ryhel
2026-02-09 10:44 ` [PATCH v2 4/9] mfd: Add driver for Asus Transformer embedded controller Svyatoslav Ryhel
2026-03-06 9:18 ` Lee Jones
2026-03-06 12:36 ` Svyatoslav Ryhel
2026-02-09 10:44 ` [PATCH v2 5/9] input: serio: Add driver for Asus Transformer dock keyboard and touchpad Svyatoslav Ryhel
2026-02-09 10:44 ` [PATCH v2 6/9] input: keyboard: Add driver for Asus Transformer dock multimedia keys Svyatoslav Ryhel
2026-02-09 10:44 ` [PATCH v2 7/9] leds: Add driver for Asus Transformer LEDs Svyatoslav Ryhel
2026-03-06 10:04 ` Lee Jones
2026-03-06 12:45 ` Svyatoslav Ryhel
2026-03-09 19:04 ` Lee Jones
2026-02-09 10:44 ` [PATCH v2 8/9] power: supply: Add driver for Asus Transformer battery Svyatoslav Ryhel
2026-02-09 10:44 ` [PATCH v2 9/9] 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=ec3b39d6-51ec-429d-b083-e5af2b4a9c65@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.