linux-kernel - platform device initialization order

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>] [day] [month] [year] [list]

Message-ID: <e5067620-a96c-fb87-2596-6cc10535c3aa@metux.net>
Date:   Wed, 16 Jan 2019 22:29:26 +0100
From:   "Enrico Weigelt, metux IT consult" <lkml@...ux.net>
To:     LKML <linux-kernel@...r.kernel.org>,
        Andreas Pretzsch <apr@...eng.de>
Subject:  platform device initialization order

Hi folks,

I'm currently writing a x86 board driver which makes use of a gpio
chip driver, gpio-leds and gpio-keyboard driver.

The init function fist initializes the gpio device, then the others,
via platform_device_register_resndata().

Here my problem starts: when the gpio driver is built as a module,
the order is mixed up - gpio driver is probed *after* the others
that need the gpio's. So, the gpio's aren't available yet, thus the
other drivers cant be initialized. If it's built-in, the order is
correct. A nasty timing problem.

Is there any way I can force the correct initialization order ?

thx
--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287