From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Lee Jones <lee.jones@linaro.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Doug Anderson <dianders@chromium.org>,
Simon Glass <sjg@chromium.org>,
Bill Richardson <wfrichar@chromium.org>,
Andrew Bresticker <abrestic@chromium.org>,
Derek Basehore <dbasehore@chromium.org>,
Todd Broch <tbroch@chromium.org>, Olof Johansson <olof@lixom.net>,
Andreas Faerber <afaerber@suse.de>,
linux-i2c@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v3 6/6] mfd: cros_ec: Instantiate sub-devices from device tree
Date: Thu, 18 Sep 2014 09:49:28 +0200 [thread overview]
Message-ID: <541A8E88.6050707@collabora.co.uk> (raw)
In-Reply-To: <20140917163114.GL30918@lee--X1>
Hello Lee,
On 09/17/2014 06:31 PM, Lee Jones wrote:
>>
>> -static const struct mfd_cell cros_devs[] = {
>> - {
>> - .name = "cros-ec-keyb",
>> - .id = 1,
>> - .of_compatible = "google,cros-ec-keyb",
>> - },
>> - {
>> - .name = "cros-ec-i2c-tunnel",
>> - .id = 2,
>> - .of_compatible = "google,cros-ec-i2c-tunnel",
>> - },
>> -};
>> -
>> int cros_ec_register(struct cros_ec_device *ec_dev)
>> {
>> struct device *dev = ec_dev->dev;
>> + struct device_node *node = dev->of_node;
>> int err = 0;
>>
>> if (ec_dev->din_size) {
>> @@ -140,12 +129,12 @@ int cros_ec_register(struct cros_ec_device *ec_dev)
>>
>> mutex_init(&ec_dev->lock);
>>
>> - err = mfd_add_devices(dev, 0, cros_devs,
>> - ARRAY_SIZE(cros_devs),
>> - NULL, ec_dev->irq, NULL);
>> - if (err) {
>> - dev_err(dev, "failed to add mfd devices\n");
>> - return err;
>
> So these devices will only ever probe with DT now ...
>
Well, these are preparatory patches to reduce the delta between upstream and
the downstream so the missing functionality could be added. One of the missing
drivers is the cros_ec_dev.c [0] which allows user-space to access the
ChromeOS Embedded Controller using a virtual character device (/dev/cros_ec).
Since that is a virtual device, it does not fit on the DT which only describes
hw and also is used on x86 machines so that subdevice is still probed using
mfd_add_devices() and the mfd_cells array is not empty in the downstream
cros_ec driver [1].
That's why I didn't just made the cros_ec MFD to depend on OF, since I didn't
want to diverge too much from the downstream driver because the idea of the
series was to reduce the difference in order to add the missing bits on top.
>> + if (node) {
>
> So it would be wrong for dev->of_node not to be populated.
>
As explained above, DT, non-DT and x86 platforms instantiate the cros-ec-dev
cells but DT platforms can define other child nodes. But I can remove the
conditional if you want and reintroduce it once cros-ec-dev support is added.
>> + err = of_platform_populate(node, NULL, NULL, dev);
>> + if (err) {
>> + dev_err(dev, "Failed to register subordinate devices");
>> + return err;
>> + }
>> }
>>
>> dev_info(dev, "Chrome EC device registered\n");
>
Best regards,
Javier
[0]:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.8/drivers/mfd/cros_ec_dev.c
[1]:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-3.8/drivers/mfd/cros_ec.c#93
next prev parent reply other threads:[~2014-09-18 7:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 9:38 [PATCH v3 0/6] Second batch of cleanups for cros_ec Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 1/6] mfd: cros_ec: Delay for 50ms when we see EC_CMD_REBOOT_EC Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 4/6] mfd: cros_ec: move locking into cros_ec_cmd_xfer Javier Martinez Canillas
[not found] ` <1410428289-18229-1-git-send-email-javier.martinez-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2014-09-11 9:38 ` [PATCH v3 2/6] i2c: i2c-cros-ec-tunnel: Set retries to 3 Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 3/6] mfd: cros_ec: stop calling ->cmd_xfer() directly Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 5/6] mfd: cros_ec: wait for completion of commands that return IN_PROGRESS Javier Martinez Canillas
2014-09-17 16:23 ` Lee Jones
2014-09-18 7:42 ` Javier Martinez Canillas
2014-09-11 9:38 ` [PATCH v3 6/6] mfd: cros_ec: Instantiate sub-devices from device tree Javier Martinez Canillas
[not found] ` <1410428289-18229-7-git-send-email-javier.martinez-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2014-09-17 16:31 ` Lee Jones
2014-09-18 7:49 ` Javier Martinez Canillas [this message]
2014-09-18 15:33 ` Javier Martinez Canillas
[not found] ` <541A8E88.6050707-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2014-09-19 0:15 ` Lee Jones
2014-09-25 13:53 ` Javier Martinez Canillas
2014-09-25 14:48 ` Lee Jones
2014-09-25 15:42 ` Javier Martinez Canillas
[not found] ` <542437DE.4090701-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2014-09-26 7:21 ` Lee Jones
2014-09-26 7:47 ` Javier Martinez Canillas
2014-09-29 7:33 ` Javier Martinez Canillas
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=541A8E88.6050707@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=abrestic@chromium.org \
--cc=afaerber@suse.de \
--cc=dbasehore@chromium.org \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sjg@chromium.org \
--cc=tbroch@chromium.org \
--cc=wfrichar@chromium.org \
--cc=wsa@the-dreams.de \
/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