All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Pi-Hsun Shih <pihsun@chromium.org>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Benson Leung <bleung@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 6/7] mfd: cros_ec: differentiate SCP from EC by feature bit.
Date: Wed, 12 Jun 2019 09:40:29 +0100	[thread overview]
Message-ID: <20190612084029.GB4797@dell> (raw)
In-Reply-To: <20190603034529.154969-7-pihsun@chromium.org>

On Mon, 03 Jun 2019, Pi-Hsun Shih wrote:

> System Companion Processor (SCP) is Cortex M4 co-processor on some
> MediaTek platform that can run EC-style firmware. Since a SCP and EC
> would both exist on a system, and use the cros_ec_dev driver, we need to
> differentiate between them for the userspace, or they would both be
> registered at /dev/cros_ec, causing a conflict.
> 
> Signed-off-by: Pi-Hsun Shih <pihsun@chromium.org>
> Acked-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
> Changes from v9:
>  - Remove changes in cros_ec_commands.h (which is sync in
>    https://lore.kernel.org/lkml/20190518063949.GY4319@dell/T/).
> 
> Changes from v8:
>  - No change.
> 
> Changes from v7:
>  - Address comments in v7.
>  - Rebase the series onto https://lore.kernel.org/patchwork/patch/1059196/.
> 
> Changes from v6, v5, v4, v3, v2:
>  - No change.
> 
> Changes from v1:
>  - New patch extracted from Patch 5.
> ---
>  drivers/mfd/cros_ec_dev.c   | 10 ++++++++++
>  include/linux/mfd/cros_ec.h |  1 +
>  2 files changed, 11 insertions(+)

Applied, thanks.

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

  reply	other threads:[~2019-06-12  8:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  3:45 [PATCH v10 0/7] Add support for mt8183 SCP Pi-Hsun Shih
2019-06-03  3:45 ` Pi-Hsun Shih
2019-06-03  3:45 ` Pi-Hsun Shih
2019-06-03  3:45 ` Pi-Hsun Shih
2019-06-03  3:45 ` [PATCH v10 1/7] dt-bindings: Add a binding for Mediatek SCP Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45 ` [PATCH v10 2/7] remoteproc/mediatek: add SCP support for mt8183 Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45 ` [PATCH v10 3/7] remoteproc: mt8183: add reserved memory manager API Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45 ` [PATCH v10 4/7] rpmsg: add rpmsg support for mt8183 SCP Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45 ` [PATCH v10 5/7] dt-bindings: Add binding for cros-ec-rpmsg Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-12  8:40   ` Lee Jones
2019-06-03  3:45 ` [PATCH v10 6/7] mfd: cros_ec: differentiate SCP from EC by feature bit Pi-Hsun Shih
2019-06-12  8:40   ` Lee Jones [this message]
2019-06-03  3:45 ` [PATCH v10 7/7] arm64: dts: mt8183: add scp node Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih
2019-06-03  3:45   ` Pi-Hsun Shih

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=20190612084029.GB4797@dell \
    --to=lee.jones@linaro.org \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=groeck@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pihsun@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 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.