On Tue, Mar 21, 2023 at 9:34 AM Sudeep Holla <sudeep.holla@xxxxxxx> wrote: > > On Mon, Mar 20, 2023 at 09:17:16AM -0500, Rob Herring wrote: > > > > This sounds like an issue for any amba driver. If this is an issue, > > solve it for everyone, not just work around it in one driver. > > > > Well it is an issue in general for power management. ACPI has specific > methods that can be executed for entering specific states. > > The way AMBA was glue into ACPI bus scan IMO was a hack and PM wasn't > considered at the time. It was just hack to get AMBA drivers to work > with ACPI without any consideration about runtime PM or any methods that > comes as part of ACPI device. There is even some dummy clock handler to > deal with AMBA requesting APB clocks. AMBA device is added as companion > to the ACPI device created as part of the normal bus scan in ACPI which > adds its own PM callbacks and rely on clocks and power domains independent > of the ACPI standard methods(_ON/_OFF). I thought only DT had hacks... ;) > The default enumeration adds platform devices which adds no extra PM > callbacks and allows normal acpi_device probe flow. > > > When someone puts another primecell device into an ACPI system, are we > > going to go do the same one-off change in that driver too? (We kind of > > already did with SBSA UART...) > > > > I would prefer to move all the existing users of ACPI + AMBA to move away > from it and just use platform device. This list is not big today, bunch > of coresight, PL061/GPIO and PL330/DMA. And all these are assumed to be > working or actually working if there is no need for any power management. > E.g. on juno coresight needs PM to turn on before probing and AMBA fails > as dummy clocks are added but no power domains attached as ACPI doesn't > need deal with power domains in the OSPM if it is all well abstracted in > methods like _ON/_OFF. They are dealt with explicit power domain in the > DT which needs to be turned on and AMBA relies on that. > > One possible further hacky solution is to add dummy genpd to satisfy AMBA > but not sure if we can guarantee ordering between ACPI device calling ON > and its companion AMBA device probing so that the power domain is ON before > AMBA uses the dummy clock and power domains in its pm callback hooks. What if we made AMBA skip its usual matching by ID and only use DT/ACPI style matching? We have specific compatibles, but they have never been used by the kernel. The only reason the bus code needs to do PM is reading the IDs which could be pushed into the drivers that need to match on specific IDs (I suspect we have some where the compatible is not specific enough (old ST stuff)). Looks like we only have 2 platforms left not using DT: arch/arm/mach-ep93xx/core.c: amba_device_register(&uart1_device, &iomem_resource); arch/arm/mach-ep93xx/core.c: amba_device_register(&uart2_device, &iomem_resource); arch/arm/mach-ep93xx/core.c: amba_device_register(&uart3_device, &iomem_resource); arch/arm/mach-s3c/pl080.c: amba_device_register(&s3c64xx_dma0_device, &iomem_resource); arch/arm/mach-s3c/pl080.c: amba_device_register(&s3c64xx_dma1_device, &iomem_resource); Get rid of these cases and we don't have to worry about non-DT or ACPI matching. > Even the UART would fail if it needed any PM methods, we just don't happen > to need that for SBSA and may be we could have made it work as amba device > (can't recollect the exact reason for not doing so now). SBSA doesn't require ID registers. SBSA UART is a "great" example of none of the existing 2 standards work, so let's create a 3rd. Rob
