All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Rushikesh S Kadam <rushikesh.s.kadam@intel.com>
Cc: bleung@chromium.org, enric.balletbo@collabora.com,
	groeck@chromium.org, linux-kernel@vger.kernel.org,
	gwendal@google.com, jettrink@chromium.org,
	andriy.shevchenko@intel.com
Subject: Re: [PATCH v3] mfd: cros_ec: instantiate properly CrOS ISH MCU device
Date: Tue, 2 Apr 2019 06:13:17 +0100	[thread overview]
Message-ID: <20190402051317.GS4187@dell> (raw)
In-Reply-To: <1551428454-596-1-git-send-email-rushikesh.s.kadam@intel.com>

On Fri, 01 Mar 2019, Rushikesh S Kadam wrote:

> 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>
> ---
> v3
> - Dropped "Intel" in commments in cros_ec header file. CrOS EC ISH
>   device is a generic ISH. This was missed earlier. 
> v2
> - Addressed review comments to term the CrOS EC device as a generic
>   Integrated Sensor Hub. 
> v1
> - Initial version.
> 
>  drivers/mfd/cros_ec_dev.c            | 13 +++++++++++++
>  include/linux/mfd/cros_ec.h          |  1 +
>  include/linux/mfd/cros_ec_commands.h |  2 ++
>  3 files changed, 16 insertions(+)

Applied, thanks.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      parent reply	other threads:[~2019-04-02  5:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01  8:20 [PATCH v3] mfd: cros_ec: instantiate properly CrOS ISH MCU device Rushikesh S Kadam
2019-03-01  9:50 ` Enric Balletbo i Serra
2019-03-01 16:19   ` Gwendal Grignou
2019-03-18 15:23 ` Andy Shevchenko
2019-04-02  5:13 ` Lee Jones [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=20190402051317.GS4187@dell \
    --to=lee.jones@linaro.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=gwendal@google.com \
    --cc=jettrink@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rushikesh.s.kadam@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.