lkml.org 
[lkml]   [2017]   [Nov]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH v2] platform/x86: wmi-bmof: New driver to expose embedded Binary WMI MOF metadata
On Thu, Nov 23, 2017 at 6:39 AM, Pali Rohár <pali.rohar@gmail.com> wrote:
> On Tuesday 04 July 2017 15:28:19 Pali Rohár wrote:
>> On Tuesday 06 June 2017 22:50:52 Pali Rohár wrote:
>> > On Tuesday 06 June 2017 19:02:01 Darren Hart wrote:
>> > > On Tue, Jun 06, 2017 at 12:04:40PM +0200, Pali Rohár wrote:
>> > > > On Monday 05 June 2017 20:16:44 Andy Lutomirski wrote:
>> > > > > +#define WMI_BMOF_GUID "05901221-D566-11D1-B2F0-00A0C9062910"
>> > > > > +MODULE_ALIAS("wmi:" WMI_BMOF_GUID);
>> > > >
>> > > > Cannot we generate MODULE_ALIAS from module_wmi_driver()? IIRC it
>> > > > is working for i2c drivers.
>> > >
>> > > I could see this being automated since we always use wmi:GUID, but it
>> > > isn't currently. Happy to consider it as a follow on.
>> > >
>> > > Do you have a specific i2c example you think we should consider
>> > > following?
>> >
>> > For i2c you can specify in driver code:
>> >
>> > MODULE_DEVICE_TABLE(i2c, id_table);
>> >
>> > And it automatically provides (via file.mod.c) all needed MODULE_ALIAS.
>> >
>> > So when we have wmi_bmof_id_table in driver, cannot we use this?
>> >
>> > MODULE_DEVICE_TABLE(wmi, wmi_bmof_id_table);
>>
>> Just reminder for above idea ↑↑↑
>
> Hi! This email is some months old, so do not know if something was
> implemented or not. Does somebody know?
>

I don't think so. I was way too lazy.

\
 
 \ /
  Last update: 2017-11-23 15:49    [W:0.070 / U:8.500 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site