On 8/24/25 6:00 PM, Krzysztof Kozlowski wrote: > On 22/08/2025 17:03, Tudor Ambarus wrote: >> Hi, Rob, >> >> On 8/22/25 2:55 PM, Rob Herring wrote: >>> On Tue, Aug 19, 2025 at 11:45:36AM +0000, Tudor Ambarus wrote: >>>> The firmware exposes clocks that can be controlled via the ACPM >>>> interface. Describe the clocks exposed by the APM firmware. >>> >>> ACPM? APM is Advanced Power Management aka the predecessor to ACPI? >> >> ACPM (Alive Clock and Power Manager) is a firmware that operates on the > > Please unwrap the acronym in one place of bindings commit msgs. Okay. > >> APM (Active Power Management) module that handles overall power management >> activities. APM is built around a GREBE processor. >> >> In linux we have an ACPM protocol driver that communicates with the firmware >> via mailbox channels. It's similar to arm,scmi if you want. > > Rest of Rob's comment seems valid, so this also invalidates the DTS. > I assume Rob and you are suggesting to drop the child node and add #clock-cells to the parent. Then define the specific clock data in the parent and create a platform device by hand for the clocks with platform_device_register_data(). I think this works well as what's used in the kernel is just the clock mailbox channel id, clock IDs and clock names. And these can be defined with parent's compatible data. Please correct me if I understood it wrong. Cheers, ta
