Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5997918imu; Wed, 30 Jan 2019 07:08:22 -0800 (PST) X-Google-Smtp-Source: ALg8bN6fcEPrVhQD8i64Tj/8/Vsrv3MfqCnX9EvPDKi4KeMGFrmlwDTH41jQW1njN0fQbe8nne+/ X-Received: by 2002:a17:902:7896:: with SMTP id q22mr31230974pll.280.1548860902243; Wed, 30 Jan 2019 07:08:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548860902; cv=none; d=google.com; s=arc-20160816; b=nb7E3d/9tW/Kg4IKupd3wYpE7gAcbCk/9Pezyxffnq+kKeQamjcj3S45eVDGFa06jO ymus3cRUMOuicSExgqsPJ2XBEblUuGxGQGnHO/gXpmPKOzhN0bd02hjTmatBv7t6Qys/ OIqDbhYIDIPRidUJY3GmsJLdLuuSbVaS6vkOOThzmChAHspcmJkWoIco+PXCk6tlYj4l RAmlwxdwcilbtCOuL2jl37R3zZArPg0GVOt1EAaAgrNKiXVKi74yBP88hktFgsqrKe6c JVWlNgYWiXHEI1ThfjzvubvAhFalF3z8vhp8m1hdOi7XOquiZpEMkxeONWv5qmQg/rRV KXhw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=fRCmJioATJL5WYGPiQvnI00ogVwM6ieigySHAUm7H0w=; b=IvMP1ZnkYN24nU7yh98I8qxlkcNqD85hNDyx7jgBayDLM8Jibz9xzTtp2G+CkeAiH+ md+MWphA6Fz1vp74s080LLMn6zYgKb1aAiFIPC4IUqxNsc6vn7Nkx15Ts5pQpaZo7Cee inojylcCKG+R/jwXhafo0gpcXVlWCtApoQL4y5iQoaIL41GrWU6rcWiG5eR7kavJmfNy D2sfbufdug/QcHCQyX1EtIzH1LuQNuF4vhhgW6zEfYGtKrcd/lLSzPMjiHF7NNGJfCWM E8G6tU2mFNoXgLZCqWxi/aaeJAzzlzXBnve0rKKJzPy1g6ZVu4JqTkuZ9KFoakPJx3V8 bkWw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=NcdpxPVm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y7si1620817pgc.236.2019.01.30.07.07.56; Wed, 30 Jan 2019 07:08:22 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=NcdpxPVm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731459AbfA3PGW (ORCPT + 99 others); Wed, 30 Jan 2019 10:06:22 -0500 Received: from mail-qt1-f194.google.com ([209.85.160.194]:36016 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727162AbfA3PGU (ORCPT ); Wed, 30 Jan 2019 10:06:20 -0500 Received: by mail-qt1-f194.google.com with SMTP id t13so26532249qtn.3 for ; Wed, 30 Jan 2019 07:06:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=fRCmJioATJL5WYGPiQvnI00ogVwM6ieigySHAUm7H0w=; b=NcdpxPVm5QS3oX2P3MqCk8+rZV2yMw7n8XE0GHi670d1YCK3PdRxGt06foxuCb4Es5 LD3+Zyil4xgws2q9WwO6+f8mGAI+0xfRX4PiRGdQa2rGG31ntX9PxALEwYfLNAiixayJ XDJINutv9+G46lrV6ph8TS3OXAmpz5VsqMG6YMw/6qkrtX4hGo6rLCq5Smgam7yoysC3 XMOWkIAlR/MbTqcyVW3mod2LOPdqRNtraUgVbkwahZl2BDKAiswBKSbzG54fFW4GvF0D rTKBcBQWfGiLmYv0gCNKODFfv6F1zP9b7WIVq3OPcKOvCCICTLDS5q0x54zHQMMJO3Xk DUxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=fRCmJioATJL5WYGPiQvnI00ogVwM6ieigySHAUm7H0w=; b=WB1sqYa2hecYEOf+efmp67LmSZNSaHOdYbBMKv0KxEXotUowqGJTIVUx6ooFk4kgs+ 6J63HUcHBaXxKCQWdNPI2TWnEW3bGHLDBbZs72zpTAlRqGmSBRPODLxITMAc7uOyZlOE aJaod3XtIlhH5NIHJ2qp7gJNPaM+ARHArw445rHYRlbQZ4Zhi7bvL873W25dZqw+ucLc jqVID48ujJfqfE4iHrRD62sWG5+8HQ7p3Zqu68DvZkgeu3AAz+l6ZxgEt5V8HA4OmW04 JJpMcZ3YsxOJNXyac2ujiCjOZLSxd86fSn3Jx58W693o+zpSYZX78FM1CLKIh8Hq3lEj YTtw== X-Gm-Message-State: AHQUAuautqmdLQJ6vF/wgn+ldBICD23JDXgu/SGOXG3xf5+inF4Yps+7 qHk6V3DeQTlTdEbU0/LoFR7cHtuvA2JSTx0FbDQ= X-Received: by 2002:ac8:4284:: with SMTP id o4mr9259179qtl.389.1548860779118; Wed, 30 Jan 2019 07:06:19 -0800 (PST) MIME-Version: 1.0 References: <20190121071833.43443-1-pihsun@chromium.org> <20190121071833.43443-6-pihsun@chromium.org> <20190130130738.GC4701@dell> In-Reply-To: <20190130130738.GC4701@dell> From: Enric Balletbo Serra Date: Wed, 30 Jan 2019 16:06:08 +0100 Message-ID: Subject: Re: [RFC v3 5/5] cros_ec: differentiate SCP from EC by feature bit. To: Lee Jones Cc: Pi-Hsun Shih , Nicolas Boichat , Guenter Roeck , Benson Leung , Enric Balletbo i Serra , open list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Lee, Pi-Hsun, Missatge de Lee Jones del dia dc., 30 de gen. 2019 a les 14:07: > > On Mon, 21 Jan 2019, Pi-Hsun Shih wrote: > > > Since a SCP and EC would both exist on a system, and use the cros_ec_de= v > > driver, we need to differentiate between them for the userspace, or the= y > > would both be registered at /dev/cros_ec, causing a conflict. > > > > Cc: Enric Balletbo Serra > > Cc: Guenter Roeck > > Signed-off-by: Pi-Hsun Shih > > --- > > Changes from v2: > > - No change. > > > > Changes from v1: > > - New patch extracted from Patch 5. > > --- > > drivers/mfd/cros_ec_dev.c | 9 +++++++++ > > include/linux/mfd/cros_ec.h | 1 + > > include/linux/mfd/cros_ec_commands.h | 2 ++ > > 3 files changed, 12 insertions(+) > > Just to clarify to the new Cc'ed list, I'm waiting on one of the > Chromium guys to review before I put my mucky paws over it. > Pi-Hsun, is this patchset still an RFC or you really want to see this merged ASAP? If I am not mistaken there is still some work in progress trying to push all the SCP stuff? Lee, personally I have some concerns. Looks like the cros_* family is increasing quickly lately (cros_ec, cros_pd, cros_scp, cros_ish, cros_fp ...) and I am wondering if we are really doing well all this. To be honest, I'd like to take a deeper look before merge this, btw I thought there was no hurry because of the RFC and I guess there are still some scp things that are missing. I might be wrong, and if that's not the case I can take a look deeper and the end of the week. Best regards, Enric > -- > Lee Jones [=E6=9D=8E=E7=90=BC=E6=96=AF] > Linaro Services Technical Lead > Linaro.org =E2=94=82 Open source software for ARM SoCs > Follow Linaro: Facebook | Twitter | Blog