From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Enric Balletbo Serra <eballetbo@gmail.com>
Cc: Gwendal Grignou <gwendal@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Jett Rink <jettrink@chromium.org>,
Guenter Roeck <groeck@google.com>,
Rushikesh S Kadam <rushikesh.s.kadam@intel.com>,
Lee Jones <lee.jones@linaro.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Aaron Durbin <adurbin@google.com>,
Duncan Laurie <dlaurie@google.com>
Subject: Re: [PATCH] cros_ec: instantiate properly Intel ISH MCU device
Date: Thu, 28 Feb 2019 09:56:56 +0200 [thread overview]
Message-ID: <20190228075656.GA9224@smile.fi.intel.com> (raw)
In-Reply-To: <CAFqH_53CF2rOVt8G=amQXC2_0mNXZw2m8_kvkM2wMjx6GyWSaQ@mail.gmail.com>
On Thu, Feb 28, 2019 at 12:05:35AM +0100, Enric Balletbo Serra wrote:
> Missatge de Gwendal Grignou <gwendal@chromium.org> del dia dc., 27 de
> febr. 2019 a les 19:37:
> > On Wed, Feb 27, 2019 at 10:08 AM Enric Balletbo i Serra
> > <enric.balletbo@collabora.com> wrote:
> > > On 27/2/19 16:13, Jett Rink wrote:
> > You're right, the cros_ names are based on what the EC provides.
> > cros_ec for generic EC, fp, tp for fingerprint, touch pad
> > respectively.
> > ish is for standalone sensor hub [it does not have to be Intel Sensor Hub].
> >
>
> Thanks for the explanation. I didn't know that and I assumed the 'i'
> was for 'intel', maybe would be good call cros_ssh or cros_sh to avoid
> confusion?
i is for Integrated. There is no confusion.
It seems you misread what was written in [] above.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-02-28 7:57 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 [this message]
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
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=20190228075656.GA9224@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=adurbin@google.com \
--cc=bleung@chromium.org \
--cc=dlaurie@google.com \
--cc=eballetbo@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=groeck@google.com \
--cc=gwendal@chromium.org \
--cc=jettrink@chromium.org \
--cc=lee.jones@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox