public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rushikesh S Kadam <rushikesh.s.kadam@intel.com>
To: Enric Balletbo Serra <eballetbo@gmail.com>
Cc: Lee Jones <lee.jones@linaro.org>,
	Benson Leung <bleung@chromium.org>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Guenter Roeck <groeck@chromium.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Gwendal Grignou <gwendal@google.com>,
	Jett Rink <jettrink@chromium.org>,
	Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: Re: [PATCH] cros_ec: instantiate properly Intel ISH MCU device
Date: Fri, 1 Mar 2019 08:49:01 +0530	[thread overview]
Message-ID: <20190301031901.GA27120@intel.com> (raw)
In-Reply-To: <CAFqH_53uR6fJepJ7s9gYBFSE=0oviaFOgn=h0KcEjKwiTu+Btw@mail.gmail.com>

Thanks Enric, Jett, Gwendal & Andy for taking timeout to review
the patch & provide detailed inputs.

Couple of acks below.


On Thu, Feb 28, 2019 at 01:33:09PM +0100, Enric Balletbo Serra wrote:
> Hi,
> 
> Based on the discussion we had, only some few comments.
> 
> Missatge de Rushikesh S Kadam <rushikesh.s.kadam@intel.com> del dia
> dg., 24 de febr. 2019 a les 10:15:
> >
> > Intel Integrated Sensor Hub (ISH) is also a MCU running EC
> > having feature bit EC_FEATURE_ISH. Instantiate it as a special
> > CrOS EC device with device name 'cros_ish'.
> >
> > Signed-off-by: Rushikesh S Kadam <rushikesh.s.kadam@intel.com>
> > ---
> >  drivers/mfd/cros_ec_dev.c            | 10 ++++++++++
> >  include/linux/mfd/cros_ec.h          |  1 +
> >  include/linux/mfd/cros_ec_commands.h |  2 ++
> 
> Better if you use the "mfd: cros_ec:" prefix in the next version so
> it's clear that this should go through the MFD tree.

Ok, will do.

> 
> >  3 files changed, 13 insertions(+)
> >
> > diff --git a/drivers/mfd/cros_ec_dev.c b/drivers/mfd/cros_ec_dev.c
> > index 2d0fee4..be499b8 100644
> > --- a/drivers/mfd/cros_ec_dev.c
> > +++ b/drivers/mfd/cros_ec_dev.c
> > @@ -414,6 +414,16 @@ static int ec_device_probe(struct platform_device *pdev)
> >         device_initialize(&ec->class_dev);
> >         cdev_init(&ec->cdev, &fops);
> >
> > +       /* check whether this is actually a Intel ISH rather than an EC */
> 
> "Check whether this is actually an Integrated Sensor Hub (ISH) rather
> than an EC"?

Ack.

> 
> > +       if (cros_ec_check_features(ec, EC_FEATURE_ISH)) {
> > +               dev_info(dev, "Intel ISH MCU detected.\n");
> 
>  dev_info(dev, "CrOS ISH MCU detected.\n"); ?

Ack.

> 
> > +               /*
> > +                * Help userspace differentiating ECs from ISH MCU,
> > +                * regardless of the probing order.
> > +                */
> > +               ec_platform->ec_name = CROS_EC_DEV_ISH_NAME;
> > +       }
> > +
> >         /*
> >          * Add the class device
> >          * Link to the character device for creating the /dev entry
> > diff --git a/include/linux/mfd/cros_ec.h b/include/linux/mfd/cros_ec.h
> > index de8b588..00c5765 100644
> > --- a/include/linux/mfd/cros_ec.h
> > +++ b/include/linux/mfd/cros_ec.h
> > @@ -24,6 +24,7 @@
> >
> >  #define CROS_EC_DEV_NAME "cros_ec"
> >  #define CROS_EC_DEV_PD_NAME "cros_pd"
> > +#define CROS_EC_DEV_ISH_NAME "cros_ish"
> >
> >  /*
> >   * The EC is unresponsive for a time after a reboot command.  Add a
> > diff --git a/include/linux/mfd/cros_ec_commands.h b/include/linux/mfd/cros_ec_commands.h
> > index fc91082..9276c3c 100644
> > --- a/include/linux/mfd/cros_ec_commands.h
> > +++ b/include/linux/mfd/cros_ec_commands.h
> > @@ -856,6 +856,8 @@ enum ec_feature_code {
> >         EC_FEATURE_RTC = 27,
> >         /* EC supports CEC commands */
> >         EC_FEATURE_CEC = 35,
> > +       /* The MCU is an Intel Integrated Sensor Hub */
> > +       EC_FEATURE_ISH = 40,
> 
> Just a note that we will have a trivial conflict to solve with
> https://lkml.org/lkml/2019/2/27/723

Thanks

Rushikesh

> 
> >  };
> >
> >  #define EC_FEATURE_MASK_0(event_code) (1UL << (event_code % 32))
> > --
> > 1.9.1
> >
> 
> Best regards,
> Enric

-- 

      reply	other threads:[~2019-03-01  3:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24  9:13 [PATCH] cros_ec: instantiate properly Intel ISH MCU device Rushikesh S Kadam
     [not found] ` <CABXOdTdprS1OL534XQq8yHTFDzXdWWODq3VGrSEHYe2wmV5zfg@mail.gmail.com>
     [not found]   ` <CAK+PMK67rWZarOV31n=yYbRMq3wo9vDyMTQ93PFZ7PRUMS66Ng@mail.gmail.com>
     [not found]     ` <CABXOdTdbev2nKNjocqxOyPcGOU8zbWpQ7uALWZdEHL0CXkYDgA@mail.gmail.com>
     [not found]       ` <CAK+PMK5U4YRtJNUbsQu3ARJFxwai7W=DjPfjuX_AZMFcUZ-c_A@mail.gmail.com>
2019-02-27 14:22         ` Enric Balletbo i Serra
2019-02-27 15:13           ` Jett Rink
2019-02-27 18:08             ` Enric Balletbo i Serra
2019-02-27 18:34               ` Gwendal Grignou
2019-02-27 23:05                 ` Enric Balletbo Serra
2019-02-28  7:56                   ` Andy Shevchenko
2019-02-28 12:17                     ` Enric Balletbo Serra
2019-02-28 23:39                       ` Gwendal Grignou
2019-02-28 12:33 ` Enric Balletbo Serra
2019-03-01  3:19   ` Rushikesh S Kadam [this message]

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=20190301031901.GA27120@intel.com \
    --to=rushikesh.s.kadam@intel.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=bleung@chromium.org \
    --cc=eballetbo@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=gwendal@google.com \
    --cc=jettrink@chromium.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox