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:   Fri, 15 Oct 2021 20:50:13 +0200
From:   Hans de Goede <>
To:     Mark Brown <>
Cc:     "Rafael J . Wysocki" <>,
        Mark Gross <>,
        Andy Shevchenko <>,
        Daniel Scally <>,
        Laurent Pinchart <>,
        Mauro Carvalho Chehab <>,
        Liam Girdwood <>,
        Michael Turquette <>,
        Stephen Boyd <>, Len Brown <>,,,,
        Sakari Ailus <>,
        Kate Hsuan <>,,
Subject: Re: [PATCH 05/12] regulator: Introduce tps68470-regulator driver


On 10/15/21 6:46 PM, Mark Brown wrote:
> On Mon, Oct 11, 2021 at 01:43:40PM +0200, Hans de Goede wrote:
>> To make this work when everything is build as a module patch 12/12
>> adds the following to the PMIC-MFD-driver:
>> MODULE_SOFTDEP("pre: clk-tps68470 tps68470-regulator");
>> This will make modprobe load the clk and regulator drivers
>> before it loads the main/MFD tps68470 driver.
> I feel nervous about this being reliable with all userspaces - IIRC
> there was an alternative implementation of the modules stuff in
> userspace and someone could always be doing insmod.  OTOH without better
> in kernel dependency management and/or more standards based firmware
> interfaces I guess we're stuck with this.

Right, this is all less then ideak, but I believe that this is the
best we can do for now.

Are you happy with the platform_data for this driver as defined in
patch 4/12 ? :

And are you ok with me doing an immutable-branch based on
5.15-rc1 with just the patch adding the platform_data
in there ?  The platform_data is used/shared by most patches
in this series. So the idea is to have an immutable branch
which can be shared/merged by all subsystems which have
patches in this patch series.



Powered by blists - more mailing lists