[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 02 Feb 2015 12:57:08 +0100
From: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
To: Paul Bolle <pebolle@...cali.nl>
CC: Lee Jones <lee.jones@...aro.org>, Olof Johansson <olof@...om.net>,
Arnd Bergmann <arnd@...db.de>,
Doug Anderson <dianders@...omium.org>,
Bill Richardson <wfrichar@...omium.org>,
Simon Glass <sjg@...gle.com>,
Gwendal Grignou <gwendal@...gle.com>,
Jonathan Corbet <corbet@....net>,
Varka Bhadram <varkabhadram@...il.com>,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 3/7] misc: Add cros_ec_lpc driver for x86 devices
Hello,
On 01/30/2015 01:51 PM, Javier Martinez Canillas wrote:
> On 01/29/2015 10:11 PM, Paul Bolle wrote:
>>> + help
>>> + If you say Y here, you get support for talking to the ChromeOS EC
>>> + over an LPC bus. This uses a simple byte-level protocol with a
>>> + checksum. This is used for userspace access only. The kernel
>>> + typically has its own communication methods.
>>> +
>>
>> What happens when you say M?
>>
>
> Since it is a tristate kconfig symbol, it can be built as a kernel module
> but since there isn't a LPC subsystem, the platform device is registered
> in the module_init() function. So, building as a module is trickier since
> there won't be an uevent that can trigger a module auto-load based on the
> modinfo aliases information.
>
FYI, I noticed that other x86 platform drivers use the dmi system information
to fill dmi modaliases so the modules are auto-loaded. So I did the same and
posted a new version 5 [0] of this series.
Best regards,
Javier
[0]: https://lkml.org/lkml/2015/2/2/214
--
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/
Powered by blists - more mailing lists