linux-kernel - Re: [PATCH v4 0/4] add device drivers for Siemens Industrial PCs

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: <a1a6c43d-401c-19f1-9773-696402974f6b@roeck-us.net>
Date:   Fri, 26 Nov 2021 08:02:11 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Henning Schild <henning.schild@...mens.com>,
        linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org,
        platform-driver-x86@...r.kernel.org, linux-watchdog@...r.kernel.org
Cc:     Srikanth Krishnakar <skrishnakar@...il.com>,
        Jan Kiszka <jan.kiszka@...mens.com>,
        Gerd Haeussler <gerd.haeussler.ext@...mens.com>,
        Wim Van Sebroeck <wim@...ux-watchdog.org>,
        Mark Gross <mgross@...ux.intel.com>,
        Hans de Goede <hdegoede@...hat.com>,
        Pavel Machek <pavel@....cz>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Enrico Weigelt <lkml@...ux.net>
Subject: Re: [PATCH v4 0/4] add device drivers for Siemens Industrial PCs

On 11/26/21 7:34 AM, Henning Schild wrote:
> Hi all,
> 
> in p3 not too much was left open so i hope this might be the last and
> might be quick.
> 
> The two points that have been open where:
>   1 wish to split wdt driver into two
>   2 wish to use pinctrl for LEDs/WDT
> 
> 1 was ignored for now. We can split later when we add more devices. It
> remains unclear if splitting is the way to go when more devices come.

The code is already quite messy, in part because memory regions are
declared locally and not passed through the parent device as they should.
I don't see how splitting the driver into multiple drivers would improve
the situation. The platform code claims to be inspired by the lpc_ich
driver. Maybe it should take a real example from that and pass version
or variant specific details through platform data instead of maintaining
it in the watchdog driver.

Guenter