linux-kernel - Re: [PATCH] dmaengine: pl330: set subsys

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0db70a26-bc3f-48f4-acfc-9fc7f960252f@kernel.org>
Date:   Tue, 7 Nov 2023 11:03:27 +0100
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Bumyong Lee <bumyong.lee@...sung.com>,
        Vinod Koul <vkoul@...nel.org>,
        Philipp Zabel <p.zabel@...gutronix.de>
Cc:     dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dmaengine: pl330: set subsys_initcall level

On 31/10/2023 04:48, Bumyong Lee wrote:
> module_amba_driver is macro for module_init/exit
> module_init is device_initcall level when it configured
> with built-in driver.
> 
> pl330 is dmaengine driver. because slave drivers depend on
> dmaengine drivers, dmaengine drivers is more appropriate
> subsys_initcall.

The same is true for all resource providers and we do not manually order
them via initcalls. Sorry, this was fine as is. Implement defer for your
drivers, not hack initcalls. If you upstreamed them, then it could even
work out of the box for you .

Best regards,
Krzysztof