linux-kernel - [PATCH v5 6/9] mfd: cros_ec: Add DT property to define ChromeOS EC name

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1433336644-20532-7-git-send-email-javier.martinez@collabora.co.uk>
Date:	Wed,  3 Jun 2015 15:04:01 +0200
From:	Javier Martinez Canillas <javier.martinez@...labora.co.uk>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Samuel Ortiz <sameo@...ux.intel.com>,
	Olof Johansson <olof@...om.net>,
	Doug Anderson <dianders@...omium.org>,
	Bill Richardson <wfrichar@...omium.org>,
	Simon Glass <sjg@...gle.com>,
	Gwendal Grignou <gwendal@...gle.com>,
	Stephen Barber <smbarber@...omium.org>,
	Filipe Brandenburger <filbranden@...gle.com>,
	Todd Broch <tbroch@...omium.org>,
	Alexandru M Stan <amstan@...omium.org>,
	Heiko Stuebner <heiko@...ech.de>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, Gwendal Grignou <gwendal@...omium.org>,
	Javier Martinez Canillas <javier.martinez@...labora.co.uk>
Subject: [PATCH v5 6/9] mfd: cros_ec: Add DT property to define ChromeOS EC name

From: Gwendal Grignou <gwendal@...omium.org>

Chromebooks can have more than one Embedded Controller with
different functinality. For example there may be a EC that
handles Power Delivery (PD) or another one that is a Sensor
Hub (SH). So there should be a way to specify the function
so that is reflected in the character device name and the
sysfs entries.

Add a "google,cros-ec-name" DT property to the ChromeOS EC
binding document to change the EC name based on its function.

Signed-off-by: Gwendal Grignou <gwendal@...omium.org>
Reviewed-by: Doug Anderson <dianders@...omium.org>
Signed-off-by: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
---

Changes since v4: None, new patch
---
 Documentation/devicetree/bindings/mfd/cros-ec.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/mfd/cros-ec.txt b/Documentation/devicetree/bindings/mfd/cros-ec.txt
index 8009c3d87f33..dcf404d16067 100644
--- a/Documentation/devicetree/bindings/mfd/cros-ec.txt
+++ b/Documentation/devicetree/bindings/mfd/cros-ec.txt
@@ -30,6 +30,11 @@ Required properties (LPC):
 - compatible: "google,cros-ec-lpc"
 - reg: List of (IO address, size) pairs defining the interface uses
 
+Optional properties (All):
+- google,cros-ec-name: name of the EC. Can be based on its function: for
+  instance, for Sensor Hub, 'cros_sh', for Power Delivery MCU 'cros_pd'.
+  If is not present, a default name will be set (i.e: 'cros_ec').
+
 
 Example for I2C:
 
-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/