linux-kernel - Re: [PATCH v5 2/6] mfd: Add ChromeOS EC implementation

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: <20130220181746.GA15152@core.coreip.homeip.net>
Date:	Wed, 20 Feb 2013 10:17:47 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Simon Glass <sjg@...omium.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Che-Liang Chiou <clchiou@...omium.org>,
	Jonathan Kliegman <kliegs@...omium.org>,
	Luigi Semenzato <semenzato@...omium.org>,
	Olof Johansson <olofj@...omium.org>,
	Vincent Palatin <vpalatin@...omium.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Rob Herring <rob.herring@...xeda.com>,
	Rob Landley <rob@...dley.net>,
	devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH v5 2/6] mfd: Add ChromeOS EC implementation

On Wed, Feb 20, 2013 at 09:24:35AM -0800, Simon Glass wrote:
> This is the base EC implementation, which provides a high level
> interface to the EC for use by the rest of the kernel. The actual
> communcations is dealt with by a separate protocol driver which
> registers itself with this interface.
> 
> Interrupts are passed on through a notifier.
> 
> A simple message structure is used to pass messages to the
> protocol driver.
> Signed-off-by: Simon Glass <sjg@...omium.org>
> Signed-off-by: Che-Liang Chiou <clchiou@...omium.org>
> Signed-off-by: Jonathan Kliegman <kliegs@...omium.org>
> Signed-off-by: Luigi Semenzato <semenzato@...omium.org>
> Signed-off-by: Olof Johansson <olofj@...omium.org>
> Signed-off-by: Vincent Palatin <vpalatin@...omium.org>

...

>  
> +config MFD_CROS_EC
> +	bool "Support ChromeOS Embedded Controller"
> +	help
> +	  If you say Y here you get support for the ChromeOS Embedded
> +	  Controller (EC) providing keyboard, battery and power services.
> +	  You also ned to enable the driver for the bus you are using. The
> +	  protocol for talking to the EC is defined by the bus driver.

Why can't it be a module?

> +
> +#ifndef __LINUX_MFD_CROS_EC_H
> +#define __LINUX_MFD_CROS_EC_H
> +
> +struct i2c_msg;

I do not believe this is needed here.

Thanks.

-- 
Dmitry
--
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/