linux-kernel - Re: [PATCH 0/2] firmware: exynos-acpm: clients (PMIC, clocks, etc.) will become children

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

Message-ID: <f84a544c-2ca4-4a84-a90f-4c94146c11b7@kernel.org>
Date: Thu, 1 May 2025 12:02:01 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Lee Jones <lee@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Tudor Ambarus <tudor.ambarus@...aro.org>,
 Alim Akhtar <alim.akhtar@...sung.com>,
 André Draszik <andre.draszik@...aro.org>,
 Peter Griffin <peter.griffin@...aro.org>,
 Will McVicker <willmcvicker@...gle.com>, kernel-team@...roid.com,
 linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/2] firmware: exynos-acpm: clients (PMIC, clocks, etc.)
 will become children

On 01/05/2025 11:09, Lee Jones wrote:
> On Tue, 22 Apr 2025, Krzysztof Kozlowski wrote:
> 
>>
>> On Thu, 27 Mar 2025 12:54:26 +0000, André Draszik wrote:
>>> ACPM clients (PMIC, clocks, etc.) will be modeled as children of the
>>> ACPM interface.
>>>
>>> This necessitates two changes in this driver:
>>> * child platform_devices from device tree need to be populated here
>>> * child drivers will need to be able to get the ACPM handle via a
>>>   struct device_node, not via a DT property name
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [1/2] firmware: exynos-acpm: populate devices from device tree data
>>       https://git.kernel.org/krzk/linux/c/636baba9489a634c956d6f02076af6bc1725c132
>> [2/2] firmware: exynos-acpm: introduce devm_acpm_get_by_node()
>>       https://git.kernel.org/krzk/linux/c/a8dc26a0ec43fd416ca781a8030807e65f71cfc5
> 
> Can this be made available for other subsystems to pull from please?
> 
> Without it MFD is currently broken.
> 
> Ref: https://lore.kernel.org/all/fd11ee67a3d51aef6305c477b140d911da0b2af4.camel@linaro.org/
> 

Yeah, I will prepare you a stable tag.

While this wasn't clearly expressed when sending the patch? There is
some "prerequisite" note in cover letter but what does that mean? What
does the contributor expect from maintainers?


Best regards,
Krzysztof