From: Lee Jones <lee.jones@linaro.org>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
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
Subject: Re: [PATCH v2 03/10] mfd: cros_ec: Instantiate sub-devices from device tree
Date: Wed, 13 May 2015 13:10:35 +0100 [thread overview]
Message-ID: <20150513121035.GL3394@x1> (raw)
In-Reply-To: <555338F3.8030507@collabora.co.uk>
On Wed, 13 May 2015, Javier Martinez Canillas wrote:
> Hello Lee,
>
> On 05/13/2015 01:32 PM, Lee Jones wrote:
> > On Sat, 09 May 2015, Javier Martinez Canillas wrote:
> >
> >> From: Todd Broch <tbroch@chromium.org>
> >>
> >> If the EC device tree node has sub-nodes, try to instantiate them as
> >> MFD sub-devices. We can configure the EC features provided by the board.
> >>
> >> Signed-off-by: Todd Broch <tbroch@chromium.org>
> >> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> >> Tested-by: Heiko Stuebner <heiko@sntech.de>
> >> Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
> >> Tested-by: Gwendal Grignou <gwendal@chromium.org>
> >> ---
> >>
> >> Changes since v1:
> >> - Added Heiko Stuebner and Gwendal Grignou Tested-by tag
> >> - Added Gwendal Grignou Reviewed-by tag
> >> - Use automatic device ID instead of 1 as suggested by Lee Jones
> >> - Remove #ifdeffery and check for of_node to register sub-devices
> >> Suggested by Lee Jones
> >> ---
> >> drivers/mfd/cros_ec.c | 22 +++++++++++-----------
> >> 1 file changed, 11 insertions(+), 11 deletions(-)
> >>
> >> diff --git a/drivers/mfd/cros_ec.c b/drivers/mfd/cros_ec.c
> >> index c4aecc6f8373..1574a9352a6d 100644
> >> --- a/drivers/mfd/cros_ec.c
> >> +++ b/drivers/mfd/cros_ec.c
> >> @@ -17,6 +17,7 @@
> >> * battery charging and regulator control, firmware update.
> >> */
> >>
> >> +#include <linux/of_platform.h>
> >> #include <linux/interrupt.h>
> >> #include <linux/slab.h>
> >> #include <linux/module.h>
> >> @@ -109,18 +110,8 @@ EXPORT_SYMBOL(cros_ec_cmd_xfer);
> >>
> >> 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",
> >> - },
> >> - {
> >> .name = "cros-ec-ctl",
> >> - .id = 3,
> >> + .id = PLATFORM_DEVID_AUTO,
> >> },
> >> };
> >>
> >> @@ -150,6 +141,15 @@ int cros_ec_register(struct cros_ec_device *ec_dev)
> >> return err;
> >> }
> >>
> >> + if (IS_ENABLED(CONFIG_OF) && dev->of_node) {
> >
> > You don't need to check for OF. of_node will be NULL if OF isn't
> > enabled.
> >
>
> Yes, you don't need it but IS_ENABLED(CONFIG_OF) causes the check to be
> optimized away by the compiler if CONFIG_OF is not enabled AFAIK.
>
> Without the IS_ENABLED(CONFIG_OF) check, this becomes a pointless pointer
> check that will always evaluate to false on systems without CONFIG_OF
> since as you said of_node will be present when CONFIG_OF is not enabled.
> But the compiler has no way to know it will always be NULL to optimize it
> away AFAICT.
Yes, you're absolutely right. You passed the test. ;)
Acked-by: Lee Jones <lee.jones@linaro.org>
> >> + err = of_platform_populate(dev->of_node, NULL, NULL, dev);
> >> + if (err) {
> >> + mfd_remove_devices(dev);
> >> + dev_err(dev, "Failed to register sub-devices\n");
> >> + return err;
> >> + }
> >> + }
> >> +
> >> dev_info(dev, "Chrome EC device registered\n");
> >>
> >> return 0;
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-05-13 12:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 10:10 [PATCH v2 00/10] mfd: cros_ec: Add multi EC and proto v3 support Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 01/10] mfd: cros_ec: Remove parent field Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 02/10] platform/chrome: cros_ec_lpc - Use existing function to check EC result Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 03/10] mfd: cros_ec: Instantiate sub-devices from device tree Javier Martinez Canillas
2015-05-13 11:32 ` Lee Jones
2015-05-13 11:43 ` Javier Martinez Canillas
2015-05-13 12:10 ` Lee Jones [this message]
2015-05-09 10:10 ` [PATCH v2 04/10] mfd: cros_ec: Use a zero-length array for command data Javier Martinez Canillas
2015-05-11 20:19 ` Gwendal Grignou
2015-05-11 21:33 ` Javier Martinez Canillas
2015-05-11 21:47 ` Heiko Stuebner
2015-05-11 21:53 ` Javier Martinez Canillas
2015-05-13 11:10 ` Lee Jones
2015-05-13 11:37 ` Javier Martinez Canillas
2015-05-20 7:43 ` Javier Martinez Canillas
2015-05-20 11:33 ` Lee Jones
2015-05-20 11:34 ` Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 05/10] mfd: cros_ec: rev cros_ec_commands.h Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 06/10] mfd: cros_ec: add proto v3 skeleton Javier Martinez Canillas
2015-05-13 12:05 ` Lee Jones
2015-05-13 12:25 ` Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 07/10] mfd: cros_ec: add bus-specific proto v3 code Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 08/10] mfd: cros_ec: Support multiple EC in a system Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 09/10] platform/chrome: cros_ec_lpc - Add support for Google Pixel 2 Javier Martinez Canillas
2015-05-09 10:10 ` [PATCH v2 10/10] mfd: cros_ec: spi: Add delay for asserting CS Javier Martinez Canillas
2015-05-13 11:16 ` Lee Jones
2015-05-11 17:53 ` [PATCH v2 00/10] mfd: cros_ec: Add multi EC and proto v3 support Heiko Stuebner
2015-05-11 20:08 ` Alexandru Stan
2015-05-11 20:51 ` Heiko Stuebner
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=20150513121035.GL3394@x1 \
--to=lee.jones@linaro.org \
--cc=amstan@chromium.org \
--cc=dianders@chromium.org \
--cc=filbranden@google.com \
--cc=gwendal@google.com \
--cc=heiko@sntech.de \
--cc=javier.martinez@collabora.co.uk \
--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