linux-kernel - Re: [PATCH] iio: adc: Add support for TI ADC1x8s102

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]

Date:   Tue, 25 Apr 2017 14:17:23 +0200
From:   Jan Kiszka <jan.kiszka@...mens.com>
To:     Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Andy Shevchenko <andy.shevchenko@...il.com>,
        Jonathan Cameron <jic23@...nel.org>, linux-iio@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sascha Weisenberger <sascha.weisenberger@...mens.com>
Subject: Re: [PATCH] iio: adc: Add support for TI ADC1x8s102

On 2017-04-25 13:35, Mika Westerberg wrote:
> On Tue, Apr 25, 2017 at 02:27:10PM +0300, Andy Shevchenko wrote:
>>> Shipping own DSDTs is no long-term path: we would be forced to provide
>>> separate images due to a single parameter being different in the DSDTs
>>> of the 2020 and 2040. And you cannot provide any overlay to adjust the
>>> table after boot, i.e. once we know on which board we are.
>>>
>>> The dependency on meta-intel is also suboptimal (we will switch to a
>>> long-term supported kernel source soon), but that would probably be
>>> fixable.
>>
>> Mika, do you have anything to comment on the above?
> 
> You don't need to depend on meta-intel or meta-acpi. There are other
> ways to add SSDT overlays than initrd. For example your boards can stick
> them to EFI variable, the kernel can find them there. Then you don't
> need to ship a separate image per board type.
> 
> For more information see Documentation/acpi/ssdt-overlays.txt.

I'm not ACPI guru: How do we come from a SSDT to information that is
carried in the DSDT so far? How can we overload wrong information in the
built in DSDT this way? I'm all ears if we could fix our (and also the
Galileo) quirks like that!

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux