From: Gwendal Grignou <gwendal@xxxxxxxxxxxx> 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@xxxxxxxxxxxx> Reviewed-by: Doug Anderson <dianders@xxxxxxxxxxxx> Signed-off-by: Javier Martinez Canillas <javier.martinez@xxxxxxxxxxxxxxx> --- 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 devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
