linux-kernel - Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of module-wide globals

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: <CAHp75VdYqK4QnncCHeiTWqaERtzJeLO+MWTEMXL9hbqaEX0USg@mail.gmail.com>
Date:   Sat, 6 May 2017 17:23:06 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Michał Kępień <kernel@...pniu.pl>
Cc:     Darren Hart <dvhart@...radead.org>,
        Jonathan Woithe <jwoithe@...t42.net>,
        Rafael Wysocki <rjw@...ysocki.net>,
        Andy Shevchenko <andy@...radead.org>,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of
 module-wide globals

On Sat, May 6, 2017 at 5:21 PM, Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Sat, May 6, 2017 at 3:45 PM, Michał Kępień <kernel@...pniu.pl> wrote:
>
>> To be fair, one thing that may be "unnatural" with this approach is that
>> even though fujitsu-backlight would depend on fujitsu-laptop, it would
>> still have to get a handle to FUJ02E3 using:
>>
>>     acpi_get_handle(NULL, "\\_SB.FEXT", ...)
>>
>> because call_fext_func() - and thus fext_backlight() - needs to be
>> passed a handle to FUJ02E3 and the two ACPI devices (FUJ02B1 handled by
>> fujitsu-backlight and FUJ02E3 handled by fujitsu-laptop) are not related
>> from the perspective of the ACPI device hierarchy.  Unless there is a
>> better way of implementing this, in which case I am open to suggestions.
>
> There are two areas to check with:
> 1. Remote graph node
> https://lwn.net/Articles/718184/
> 2. Component framework (only works in case when all devices are
> mandatory to have).

Ah, and third one is MFD framework.

-- 
With Best Regards,
Andy Shevchenko