From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Lee Jones <lee.jones@linaro.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Olof Johansson <olof@lixom.net>,
Doug Anderson <dianders@chromium.org>,
Bill Richardson <wfrichar@chromium.org>,
Simon Glass <sjg@google.com>,
Gwendal Grignou <gwendal@google.com>,
Stephen Barber <smbarber@chromium.org>,
Filipe Brandenburger <filbranden@google.com>,
Todd Broch <tbroch@chromium.org>,
Alexandru M Stan <amstan@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Gwendal Grignou <gwendal@chromium.org>
Subject: Re: [PATCH v5 7/9] mfd: cros_ec: Support multiple EC in a system
Date: Wed, 03 Jun 2015 16:08:16 +0200 [thread overview]
Message-ID: <556F0A50.20600@collabora.co.uk> (raw)
In-Reply-To: <20150603134951.GD12304@x1>
Hello Lee,
On 06/03/2015 03:49 PM, Lee Jones wrote:
[...]
>>
>> int cros_ec_register(struct cros_ec_device *ec_dev)
>> @@ -52,14 +68,39 @@ int cros_ec_register(struct cros_ec_device *ec_dev)
>>
>> cros_ec_query_all(ec_dev);
>>
>> - err = mfd_add_devices(dev, 0, cros_devs,
>> - ARRAY_SIZE(cros_devs),
>> + if (IS_ENABLED(CONFIG_OF) && dev->of_node)
>> + ec_p.ec_name = of_get_property(dev->of_node,
>> + "google,cros-ec-name", NULL);
>
> NACK
>
> You either need to obtain this another way, or have a chat with the DT
> Maintainers and explain why this platform is special enough to break
> the normal conventions.
>
> HINT: I different compatible string is normally more amenable, but
> this will also require a DT ACK for me to take it through.
>
Ok, I'll just remove the property then. After all the driver only supports
two types of controllers currently, the normal host EC and the Power Delivery
(PD) one. And there isn't a DTS even in the downstream ChromiumOS tree that
is setting a different EC name right now.
I guess the idea of the binding was to make it future proof from when the
driver supports more types of controllers but I'll let Gwendal to comment on
this since he is the author of these patches.
>> + if (!ec_p.ec_name)
>> + ec_p.ec_name = CROS_EC_DEV_NAME;
>> +
>> + err = mfd_add_devices(ec_dev->dev, PLATFORM_DEVID_AUTO, &ec_cell, 1,
>> NULL, ec_dev->irq, NULL);
>> if (err) {
>> - dev_err(dev, "failed to add mfd devices\n");
>> + dev_err(dev, "failed to add ec\n");
>
> Might be nice to expand 'ec' so your users have half a chance in
> deciphering what just went wrong.
>
I will, thanks a lot for your feedback.
> [...]
>
Best regards,
Javier
next prev parent reply other threads:[~2015-06-03 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 13:03 [PATCH v5 0/9] mfd: cros_ec: Add multi EC and proto v3 support Javier Martinez Canillas
2015-06-03 13:03 ` [PATCH v5 1/9] mfd: cros_ec: Use a zero-length array for command data Javier Martinez Canillas
[not found] ` <1433336644-20532-1-git-send-email-javier.martinez-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>
2015-06-03 13:03 ` [PATCH v5 2/9] mfd: cros_ec: rev cros_ec_commands.h Javier Martinez Canillas
2015-06-03 13:04 ` [PATCH v5 5/9] mfd: cros_ec: add bus-specific proto v3 code Javier Martinez Canillas
2015-06-03 13:03 ` [PATCH v5 3/9] mfd: cros_ec: Move protocol helpers out of the MFD driver Javier Martinez Canillas
2015-06-03 13:03 ` [PATCH v5 4/9] mfd: cros_ec: add proto v3 skeleton Javier Martinez Canillas
2015-06-03 13:04 ` [PATCH v5 6/9] mfd: cros_ec: Add DT property to define ChromeOS EC name Javier Martinez Canillas
2015-06-03 13:04 ` [PATCH v5 7/9] mfd: cros_ec: Support multiple EC in a system Javier Martinez Canillas
2015-06-03 13:49 ` Lee Jones
2015-06-03 14:08 ` Javier Martinez Canillas [this message]
2015-06-03 13:04 ` [PATCH v5 8/9] mfd: cros_ec: spi: Add a DT property to delay asserting the CS Javier Martinez Canillas
2015-06-03 13:04 ` [PATCH v5 9/9] mfd: cros_ec: spi: Add delay for asserting CS 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=556F0A50.20600@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=amstan@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=filbranden@google.com \
--cc=gwendal@chromium.org \
--cc=gwendal@google.com \
--cc=heiko@sntech.de \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sameo@linux.intel.com \
--cc=sjg@google.com \
--cc=smbarber@chromium.org \
--cc=tbroch@chromium.org \
--cc=wfrichar@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).