From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: Rob Herring <robh@kernel.org>,
Collabora Kernel ML <kernel@collabora.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Simon Glass <sjg@chromium.org>,
Doug Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Cheng-Yi Chiang <cychiang@chromium.org>
Subject: Re: [PATCH v2 3/3] mfd: google,cros-ec: add missing properties
Date: Thu, 15 Oct 2020 08:52:29 +0200 [thread overview]
Message-ID: <0578a7e56430da42daee95aabc05850da3dcc294.camel@collabora.com> (raw)
In-Reply-To: <CA+Px+wXwEm+j2AZcaXHtoFUhe9GqaaxMRecQ7X0vu49E2OKH=A@mail.gmail.com>
On Wed, 2020-10-14 at 10:18 +0800, Tzung-Bi Shih wrote:
> The intermediate layer (i.e. codecs { ... }) breaks current code as
> you already discussed about that in previous threads:
> - of_platform_populate only creates immediate child devices.
> - the codec driver expects its parent is EC node.
Thanks for your input, I'll try to address these issues in the drivers in v3.
Cheers,
Ricardo
next prev parent reply other threads:[~2020-10-15 6:52 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
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 [this message]
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=0578a7e56430da42daee95aabc05850da3dcc294.camel@collabora.com \
--to=ricardo.canuelo@collabora.com \
--cc=bleung@chromium.org \
--cc=cychiang@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=robh@kernel.org \
--cc=sjg@chromium.org \
--cc=tzungbi@google.com \
/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).